Re: Check constrain execution timing change?
"Keith Medcalf" <[email protected]>
| Newsgroups | gmane.comp.db.sqlite.general |
|---|---|
| Organization | This Side Up |
| Message-ID | <[email protected]> |
>collect input data row >apply column affinity >fire before triggers >apply defaults, generated always, rowid etc. >apply column affinity to above columns >run constraints >store actul row >fire after triggers Actually, with generated columns it is a bit more complicated. I think: collect input data row run generated column logic including not allowing specification of values for generated columns apply column affinity fire before triggers apply defaults, rowid etc. apply column affinity to defaults, rowid, etc. changed above run constraints store actul row fire after triggers -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >collect input data row >apply column affinity >fire before triggers >apply defaults, generated always, rowid etc. >apply column affinity to above columns >run constraints >store actul row >fire after triggers _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users