| Author |
Message |
|
2008/03/27 06:37
|
|
|
rameshg
Joined: 2008/03/27
Messages: 6
Offline
|
|
|
|
1. getORMID() inclusion in POJO
In POJO code generation each class gets an extra method getORMID() automatically added. Is there a way to avoid it ?
This especially gives problem if the primary key of the child class has a different data type from the data type of primary key of the parent class, in inheritance relationship.
Compilation errors thrown because parent and child classes' getORMID return types are different.
|
|
|
|
 |
| |
|
|
2008/03/27 10:17
|
|
|
Rain
Joined: 2005/04/29
Messages: 711
Offline
|
|
|
|
Hello rameshg,
Thanks for your message and I've forwarded your issue to our engineers to follow-up. And I'll get back to you once there are any feedback. If you need any help, please do not hesitate to contact me again.
Best regards,
Rain Wong
|
|
|
|
|
| |
|
|
2008/03/27 11:31
|
|
|
Rain
Joined: 2005/04/29
Messages: 711
Offline
|
|
|
|
Hello rameshg,
Both table per class hierarchy and table per subclass strategy will not generate additional PK in subclass and therefore it will not generate the getORMID method in subclass. Do you mean you have the attributes in subclass which name is same to the PK column but having different type? It seems not a usual design.
Best regards,
Rain Wong
|
|
|
|
|
| |
