- Because it means look ups for these rows require the use of a function to match as do any FK look ups. For many databases, the query plans will not even use indexes which of course is awful.
- UsA, usa, USA, etc are all different values. You can rationalized all you want that they are, but they are not.
- Do you really need more reasons? I can keep going...
quote
+ AFAIK, and looking to JPA 2.1 specification and Hibernate Guide, I can't see any violation of the primary key used for the entity [Country].
quote This line of reasoning always makes me laugh. The spec and our docs also do not say that we cannot call System.exit on your VM whenever we want. So should that be allowed? They also don't say that we cannot delete all your data and re-create it when you try to find/load or query data. Can we do that? Shall I go on? Again, this is something we are not going to do. |
