This one time, at band camp, Pierfrancesco Marsiaj said:
PM>I reply to myself as I've been able to find an answer to my question, which
PM>might eventually save some hassle to someone else trying to fit two classes
PM>into one SQL table.
PM>
PM>The question was: "can castor cope with mapping multi
I reply to myself as I've been able to find an answer to my question, which
might eventually save some hassle to someone else trying to fit two classes
into one SQL table.
The question was: "can castor cope with mapping multiple classes to one sql
table ?"
According to an OR mapping tools comp
Hi all,
I need to reiterate a question for which I haven't been able to find an
answer.
In Castor JDO there seems to be a mandatory pattern usage when mapping
classes to SQL tables: for each class you have to provide one SQL table.
Is it possible to do differently, i.e. map two or more related
