I think, this is the problem of sqlite.
Just found it in http://sqlite.org/omitted.html
Very first item says:
---
FOREIGN KEY constraints are parsed but are not enforced. However, the
equivalent constraint enforcement can be achieved using triggers. The SQLite
source tree contains source code
<http://www.sqlite.org/cvstrac/fileview?f=sqlite/tool/genfkey.c> and
documentation
<http://www.sqlite.org/cvstrac/fileview?f=sqlite/tool/genfkey.README> for a C
program that will read an SQLite database, analyze the foreign key constraints,
and generate appropriate triggers automatically.
---
It is very likely that my initial classes were correct (just ForeignKey), and
also the database schema is correctly created by sqlobject.
Zoran
________________________________
From: petr.jakes....@gmail.com [mailto:petr.jakes....@gmail.com] On Behalf Of
Petr Jakeš
Sent: Thursday, January 08, 2009 12:29 PM
To: Zoran Bošnjak
Cc: sqlobject-discuss
Subject: Re: [SQLObject] FW: table ralations
Than maybe you can try exactly what in the example is:
child=MultipleJoin("Blocks", joinColumn="parent_id")
You can have as many children as you want (and no woman necessary ;-) )
But "one parent" only (no multiple parents - it does not work even in the real
live)
If you are looking for many-to-many relationship, try this:
http://www.sqlobject.org/SQLObject.html#many-to-many-relationships
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
