Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This question is in context with the problem mentioned in this thread.
I’m also facing the same problem while using JPA on MySQL. I could resolve it only when I changed the generation strategy to TABLE.
But the question is, what was the reason behind this problem and why changing the strategy to TABLE is the solution (this remains unanswered in the thread) ?
To have unique ids through an inheritance hierarchy (which JPA requires), you obviously cannot do that with TABLE_PER_CLASS and IDENTITY since IDENTITY works off a table, and there are now multiple “root” tables in the inheritance hierarchy.
e.g abstract base class “Base”, and subclasses “Sub1”, “Sub2”, “Sub3”.
So you have actual tables “SUB1”, “SUB2”, “SUB3”. So if using IDENTITY then this will equate to something like “autoincrement” on a column when using MySQL. Hence SUB1 has its ids, SUB2 has its ids, and SUB3 has its ids … and they are independent, hence can get collisions in id … so you no longer have unique id in the inheritance hierarchy.