Unfortunately, we can’t reproduce your problem. In fact, the error message is not related to inheritance strategy, but about discriminator. In specific, it means that no discriminator has been defined for the super class. Could you send us your project to verify this problem?
I have just test this with the latest build (20071102e) and it has failed too!!
But you can not reproduce the problem, so I must have been doing something wrong.
I investigated further on and… voila! Here are the results:
If generating code from ORM Wizard, all discriminators for table-per-hierarchy left empty (as I did) are created setting it to the class name (ok). The code generation works well.
If generating code from “Generate Code…” (last option in ORM menu) the discriminators are not automatically set, and then the code generation fails. This was the path I was following lately to generate code, because you have more options available to set. Well, this path fails. But maybe this is what the “Generate Code…” is meant for. No automatically set anything.
Well, excuse me again. This time you discovered a bug in my way of doing things
Anyway, it will be great if the error description includes what you told me. I mean “Discriminator not set (somewhere in the forest… sorry, I mean, project)”. Or even better, “Discriminator not set on CChild2” :roll:
Many thanks again, this time you have saved me lots of hours rechecking all my class inheritances on the project I’m using