Federico Granata <[EMAIL PROTECTED]> wrote: > I have two db, the main one is used from mine sw (call this db A), > the other is used from another sw (call this db B). > I open A, attach B, create a temp trigger in A triggered by insert > into a table in B and writing in a table in A > > If I insert into the table in B the trigger is triggered but if the sw > (working on B) insert the same thing in the same table the trigger do > nothing.
Each connection has its own independent temp database. You've created a temporary trigger which exists in the temp database for your connection. The trigger simply doesn't exist on the other connection. > It's possible to get the trigger run when insert is lunched from > another session ? Yes, if that other session attaches the appropriate database and creates an appropriate trigger. No, you cannot magically alter the behavior of another application you have no control over. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
