Changes between Initial Version and Version 1 of Ticket #13711, comment 20
- Timestamp:
- Jun 19, 2014, 2:16:45 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13711, comment 20
initial v1 1 1 One approach: 2 2 3 Adding a setting which tells whether `truncate_name` is called or not, like `connection.support_auto_truncation` and then running the model check only for those dbs which have this set to False. 3 Adding a attribute which tells whether `truncate_name` is called or not, like `connection.supports_auto_truncation` and then running the model check only for those dbs which have this set to False. 4 5 EDITS: 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.