| 6 | | This could be similar to the one which was removed:`connection.supports_long_model_names`(This was used for the dbs which either did truncation calling truncate_name or by itself by skipping the chars after its max limit. This second part created problems). It would be like renaming this attribute to the above because the earlier use created problems and the new usage for checking only usage of `truncate_name` does not. |
| 7 | | This should be `True` for any new `3rd-party backends` that uses `truncate_name`. |
| | 6 | This could be similar to the one which was removed:`connection.supports_long_model_names`(This was used for the dbs which either did truncation calling `truncate_name` or by itself by skipping the chars after its max limit. This second part created problems). It would be like renaming this attribute to the above and correcting its usage because the earlier use created problems and the new usage for checking only usage of `truncate_name` does not. |
| | 7 | This should be `True` for any `backends` that uses `truncate_name`. |