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
This is a follow-up patch for the change introduced in #764.
It makes the Table class act more intelligent when it comes to preferring explicit over implicit indexes.
Currently it is necessary to construct a Table instance in a specific order to not have unnecessary duplicate indexes because of foreign keys. If you first add a foreign key and afterwards and explicit index that is fulfilling the implicit one, both indexes are stored. Instead it is more intelligent to replace the implicit by the explicit one if and only if the explicit one fulfills the implicit one.
This should also fix possible issues with how ORM's schema tool constructs a schema. See here where for a OneToOne relation on a primary key an additional regular index for the foreign key is created.
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of deeky666:
Url: #769
Message:
This is a follow-up patch for the change introduced in #764.
It makes the
Table
class act more intelligent when it comes to preferring explicit over implicit indexes.Currently it is necessary to construct a
Table
instance in a specific order to not have unnecessary duplicate indexes because of foreign keys. If you first add a foreign key and afterwards and explicit index that is fulfilling the implicit one, both indexes are stored. Instead it is more intelligent to replace the implicit by the explicit one if and only if the explicit one fulfills the implicit one.This should also fix possible issues with how ORM's schema tool constructs a schema. See here where for a OneToOne relation on a primary key an additional regular index for the foreign key is created.
The text was updated successfully, but these errors were encountered: