got it. Thanks.
On 2018-08-24 19:36, J Decker wrote:
On Fri, Aug 24, 2018 at 4:31 PM <w...@us.net> wrote:
"The parent key of a foreign key constraint is not allowed to use the
rowid. The parent key must used named columns only."
Why is this?
Which would be more efficient?
1) WITHOUT ROWID and column of INTEGER PRIMARY KEY
or
2) an aliased rowid.
I expect because rowid is subject to change....
insert 3 records, delete the first, and 2, 3 become 1 and 2 ... which
would
have to cascade update ALL other FK refs...
Background: The data is sparse, incomplete, and fuzzy. Two records are
known to have a relationship
even though the content that identifies this relation is not known.
Lyle Ward
Genealogist
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
