On Nov 16, 2010, at 4:19 AM, neurino wrote:
I didn't mean mapping Root to a Table (if not necessary) is my intent,
what I'd like to know is how to get the same behavior without the
bloat of an extra table.
make your application work a certain way (where certain way here is not
clear)
On Nov 15, 2010, at 8:06 AM, neurino wrote:
So no advice?
Are relationships and backref something more than attributes I can
setup with a query?
Thank you for your support.
what's not stated clearly here is what Root is. If that's not a class mapped
to a table, then you'd just need to
On Nov 15, 2010, at 10:46 AM, neurino wrote:
Thanks for your answer first.
Root is a singleton, its class is not mapped to a table.
What I mean is I could add a table roots to the database with a
sigle row and add areas a foreign key root_id and create a
relationship as from subareas
