Fri, 16 Jan 2015 12:35:46 +0100 Use a moved_entities table to record external entities moved to the system source
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 12:35:46 +0100] rev 10209
Use a moved_entities table to record external entities moved to the system source Instead of using a negative eid in the entities table, move the record to a new table so we don't have an interval with a missing eid in entities. Related to #4846892
Fri, 16 Jan 2015 12:43:32 +0100 Add unique index on entities.extid
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 12:43:32 +0100] rev 10208
Add unique index on entities.extid
Fri, 16 Jan 2015 11:17:53 +0100 [undo/test] if we try to delete an entity referenced by an inline relation, we fail
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 11:17:53 +0100] rev 10207
[undo/test] if we try to delete an entity referenced by an inline relation, we fail
Fri, 16 Jan 2015 10:56:30 +0100 [undo] when we can't undo an inlined relation change, point at None, not a broken eid
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 10:56:30 +0100] rev 10206
[undo] when we can't undo an inlined relation change, point at None, not a broken eid This whole thing is "a bit" weird.
Thu, 15 Jan 2015 19:17:32 +0100 Ask sqlite to check foreign keys
Julien Cristau <julien.cristau@logilab.fr> [Thu, 15 Jan 2015 19:17:32 +0100] rev 10205
Ask sqlite to check foreign keys Related to #4846892
Thu, 15 Jan 2015 18:53:45 +0100 Add reference from etype table's eid column to the entities table
Julien Cristau <julien.cristau@logilab.fr> [Thu, 15 Jan 2015 18:53:45 +0100] rev 10204
Add reference from etype table's eid column to the entities table Related to #4846892.
Fri, 16 Jan 2015 14:30:55 +0100 [server] change order of entities table modification vs entity creation/deletion
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 14:30:55 +0100] rev 10203
[server] change order of entities table modification vs entity creation/deletion In order to have a foreign key referencing the entities table, the insertion into entities must happen first, and the deletion must happen last. For the deletion case, this means we need to: 1. delete all relations (cascade) 2. delete the entities themselves 3. delete the corresponding lines from the entities table This means the _delete_info{,_multi} methods can't keep doing 1 and 3. Thankfully the "public" delete_info method appears to be unused, so drop it. Related to #4846892.
Thu, 15 Jan 2015 17:06:16 +0100 Use foreign keys for relations tables
Julien Cristau <julien.cristau@logilab.fr> [Thu, 15 Jan 2015 17:06:16 +0100] rev 10202
Use foreign keys for relations tables Closes #4846892
Thu, 15 Jan 2015 16:49:32 +0100 Add foreign key for inline relations
Julien Cristau <julien.cristau@logilab.fr> [Thu, 15 Jan 2015 16:49:32 +0100] rev 10201
Add foreign key for inline relations Related to #4846892
Thu, 15 Jan 2015 16:44:36 +0100 Use our version of schema2sql
Julien Cristau <julien.cristau@logilab.fr> [Thu, 15 Jan 2015 16:44:36 +0100] rev 10200
Use our version of schema2sql Related to #4846892
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip