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 the fields list in an Index contains fields that don't exist in the entity, they are silently ignored without any warning, creating an index containing only the other fields.
Note that configuring columns (expecting database column names) instead of fields (expecting names of mapped properties) is properly throwing an exception in DBAL for invalid column names. My guess is that the invalid fields are silently skipped when converting field names to column names when creating the DBAL Schema.
Bug Report
Summary
When the
fields
list in an Index contains fields that don't exist in the entity, they are silently ignored without any warning, creating an index containing only the other fields.Current behavior
How to reproduce
Expected behavior
Ideally, this should throw a MappingException. However, this is a BC break so it will need to wait until the next major version.
In the meantime, I see 2 possible improvements (not exclusive to each other):
The text was updated successfully, but these errors were encountered: