dan
|
7006c18e00
|
When updating a field that requires foreign key constraints be checked, ensure that the indexes and tables are consistent when the FK logic is run. Otherwise, it may detect the inconsistency and report database corruption.
FossilOrigin-Name: 2b3d9996a829c62fbaf7c92d50e44636340b07c6
|
2011-06-10 18:33:35 +00:00 |
|
dan
|
b328debc6a
|
Fix minor problems with foreign key constraints where the parent table is the same as the child table.
FossilOrigin-Name: 442d8d8bfe443797482354ba8766d97d3d6acaae
|
2011-06-10 16:33:25 +00:00 |
|
dan
|
e7a94d8128
|
If an update does not modify any child or parent key columns, omit foreign key processing for the statement.
FossilOrigin-Name: edff3500058eb8ad2381f855ef7a09ecb680f7b8
|
2009-10-01 16:09:04 +00:00 |
|
dan
|
856ef1a5f9
|
Various fixes so that "make test" works with OMIT_FOREIGN_KEY, OMIT_TRIGGER and OMIT_ALTER_TABLE.
FossilOrigin-Name: e4eb227b14e4bfcb9f7f284692a391b7355f0204
|
2009-09-29 06:33:23 +00:00 |
|
dan
|
d66c83095e
|
Fix the DROP TABLE command so that it cannot be used to bypass foreign key constraints (if foreign key support is enabled).
FossilOrigin-Name: 8353808c9e70412fdee31bfda7810e948f1c7485
|
2009-09-28 14:49:01 +00:00 |
|
shane
|
86d682950b
|
More fkey tests.
FossilOrigin-Name: 2d544bd53d0fb9633aca40841529aec8e7df61f8
|
2009-09-23 18:49:41 +00:00 |
|