On 9/5/2013 5:39 AM, techi eth wrote:
I have case where one process is updating data with his private handler but trigger on update is created by other process by his private handler.
I'm not sure I understand this sentence. When you run CREATE TRIGGER statement, the trigger you've just created becomes part of the database schema, visible to all connections (unless you do CREATE TEMP TRIGGER; is this what you are talking about?)
On the other hand, sqlite3_create_function() registers a custom function just for this connection. If you create a trigger that calls this function, then those connections where the function is not registered will fail to even prepare an UPDATE statement - SQLite will issue an "unknown function" error.
In general, there is no mechanism built into SQLite that would allow one process to be automatically notified that another process made a change to the database. If that's what you want, you would have to implement that in your application - you can't somehow trick SQLite into doing it for you.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users