Kees Nuyt wrote:
> That is to say, any value in id_toto2_and_toto3 has a
> corresponding row in both toto2 and toto3.
>
> You have to ask yourself if toto2 and toto3 shouldn't be
> combined into one table.
>
> As far as I can tell, the only reason to not combine them
> would be some performance optimization. One should only do
> that to solve real performance problems, not in the initial
> design.
You're right!
I just try to find the "limits" of SQL (in SQLite only) concerning foreign
keys:
* composite foreign keys
* "multiple" foreign keys as described above
* foreign key being at the same time a primary key (one-to-one relation)
For my personal use, it would be a far more simple database design.
Thanks
Julien
--
python -c "print ''.join([chr(154 - ord(c)) for c in '*9(9&(18%.\
9&1+,\'Z4(55l4('])"
"When a distinguished but elderly scientist states that something is
possible, he is almost certainly right. When he states that something is
impossible, he is very probably wrong." (first law of AC Clarke)
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
