Looks like that is getting close...but when is this called? BEFORE or AFTER?
And you also wouldn't know which trigger got called....only which table was
touched.
The dummy function would solve both those problems.
So I can still see an sqlite3_callback() either overloaded or a function
pointer replacement. Callable by an SQL function callback('Your info') or such
which gives the same info as the update_hook plus a known value under control
of the programmer.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
________________________________
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Igor Tandetnik [itandet...@mvps.org]
Sent: Friday, June 15, 2012 8:15 AM
To: sqlite-users@sqlite.org
Subject: EXT :Re: [sqlite] Triggers in Sqlite using C
Black, Michael (IS) <michael.bla...@ngc.com> wrote:
> Could the SQLite code add a new dummy function for a callback which we can
> then override with our own library?
sqlite3_update_hook
--
Igor Tandetnik
_______________________________________________
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
