You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When django create a ForeignKey field, if db_index is not explicitly specified, It set by default db_index = True.
This behavior make that django migration module creates an extra index on Foreign Key field. In Firebird adding a foreign key constraints implicitly implies that an index is added.
Then, if delete a foreign key field is required, this operation will fail because Firebird want to delete the related index.
Engine Message :
unsuccessful metadata update
column [COLUMN_NAME] from table [TABLE_NAME is referenced in index [INDEX_NAME]
can_introspect_max_length is True by default in django DatabaseFeatures
django-firebird failed to retrive the correct field length when the charset is UTF8 over a char field type
When django create a ForeignKey field, if db_index is not explicitly specified, It set by default db_index = True.
This behavior make that django migration module creates an extra index on Foreign Key field. In Firebird adding a foreign key constraints implicitly implies that an index is added.
Then, if delete a foreign key field is required, this operation will fail because Firebird want to delete the related index.
MySQL has a similar behavior.
https://github.com/django/django/blob/stable/1.8.x/django/db/backends/mysql/schema.py#L54
The text was updated successfully, but these errors were encountered: