On 2 Mar 2010, at 8:38pm, Jens Frøkjær wrote: > So, please consider this a feature request: "Deterministic order of > triggers".
I understand what you want, but I don't think you'll get it. SQL is full of ambiguity about orders. For instance suppose you execute an UPDATE command which changes many rows. There is nothing in the documentation that tells you which order those rows will be updated in. Might be in the order they were originally created. Might be in the reverse of that. Might be in some order set by some index the optimiser found convenient. Not only do different SQL engines do this differently, but version increments of one SQL engine might change how this is implemented. If statements as simple as DELETE and UPDATE don't have a deterministic execution order, I don't think the order of TRIGGER execution is going to be set in stone. Since _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
