Thanks! Something like that has already crossed my mind, but I was just wondering if there was a way to achieve that goal using the existing interfaces. Now, it looks like this solution is the only one to my problem.
Vladimir Stokic John Stanton-3 wrote: > > If you have access to the Sqlite library you can compile in yuor custom > function so that it is always available. Then your trigger will signal > a change to the DB provided that it calls the function. You could also > patch Sqlite so that it signalled your semaphore each time it executed a > COMMIT. Then you would not have to touch process A. > -- View this message in context: http://www.nabble.com/Accessing-external-applications-from-within-SQLite-triggers-tf4614175.html#a13189204 Sent from the SQLite mailing list archive at Nabble.com. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
