Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 12:43:32 +0100] rev 10208
Add unique index on entities.extid
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
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.
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
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.
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.