What do you want to have here? If you want the DB tests if the .id is
>really an id from the table A verify that SQLObject created table B with
>all necessary declarations related to referential integrity, FOREIGN KEY in
>this case. I don't remember if SQLObject 0.7 does that - I use the latest
>SQLObject from 0.7.1 branch.
>
>Oleg.
>
>
I want to have two tables with a one-to-one relationship. If I enter in
an item in TableA, there should be a corresponding record in TableB.
They should be hooked up with field [id]. This is what foreign keys are
for, right? To make sure that the two tables are consistent and have
referential integrity. I would imagine you define the primary/foreign
key in the python object. And SQLObject would take care of the nitty
gritty details.
I checked the documentation and the faq, but couldn't find any concrete
way of adding the record in SQLObject that enforces this referential
integrity. I am using SQLObject 0.7.0
- Steve
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
|
