Do you want to put that blob into all tables using a trigger or changing all applications using database? If changing applications then you can also change them to create that blob value. If using a trigger then you can insert into that trigger creation of the blob value if it doesn't exist. Is there something wrong with such solutions?
Pavel On Tue, Jun 22, 2010 at 11:35 AM, b s <gaiet...@yahoo.com> wrote: > hi, > long ago, drh had proposed a trigger like mechanism that > can be invoked at the begin/end of a transaction. > http://osdir.com/ml/db.sqlite.general/2003-04/msg00137.html > > the general consensus was there is no use other than up'ng > a counter. however, i have a requirement where i would like > to mark transaction boundaries from a user level. > > my requirement: on begin transaction, i would like to store > a hex(randomblob(16)) in a table during begin transaction and > put this value in all tables that were involved during that > transaction. > > there is no way it can be done across all connections, unless > a trigger level like facility is available. otherwise the hook functions > all work only on a sqlite connection and i dont want to load modules. > > are there any other methods available to get the same result? > or, as someone mentioned bring some Interbase like facility? > > > thanks > brs > > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users