I have an object that has two different use cases depending on the type of
user that is using the object. The Object is a subscription class. In one
use case, the subscription belongs to a mailing list that contains a list of
subscriptions. In the second use case, the subscription belongs to the to
the user and the user only needs to know what mailing list it belongs to. In
my current situation, the subscription is a child of mailing list. So when a
subscription is loaded independently of it's mailing list, the mailing list
is automatically loaded.
What I would like to do is create one subscription class for each use case
but have them both mapped to the same table. Now I know that it should be
possible to have two objects mapped to the same table, but I'm wondering of
this a a good practice and if there are any potential issues that one should
be aware of? (locking, etc.) Thanks.
Ryan-
--
"Latest survey shows that 3 out of 4 people make up 75% of the world's
population"
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
