A couple other things come to mind here, that might be relevant to what you're doing:
* A trigger that has a "final" side effect, like signaling another process, will both have that effect early (before the transaction is committed), and will have that effect even if the transaction is later rolled back. * Since database modifications are serialized, the file is updated when a change is committed. You might be able to use the OS's notifications of file modification to determine when to check for data changes. Of course, this won't tell you _what_ changed, which might not help if you're only watching for a tiny item in a large database. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
