Replies: 1 comment 7 replies
-
Not sure what you expect here, the ORM sees two values, they are not the same, there is no concept of "case insensitive" things in the ORM, that is a database engine feature. Especially here, when you use some driver-specific opt-in extension, how do you expect the ORM to respect that? I can surely fix the type error because of the mismatch, but I don't think there is a way to make this actually work (map the different case values). I also consider this as a very weird thing to do, a case insensitive PK sounds out of space to me :] |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have two entities in a Many-to-One/One-to-Many relationship, with one entity having a case-insensitive primary key. When I attempt to load both entities using 'find' and 'populate', the 'find' call will fail if there is a difference in capitalization between the two entities. However, the database handles this correctly, allowing for a manual join between the two tables.
Beta Was this translation helpful? Give feedback.
All reactions