Re: v7 triggers and OCI

In article <WHITE.93Feb22161450_at_macaw.titan.tsd.arlut.utexas.edu>, white_at_titan.tsd.arlut.utexas.edu (Eric White) writes:
> [...]
> What are the, general, steps I'd need to take to build an OCI program
> that had triggers notify it when something in a table changed?

From what I can tell, it can't be done. Triggers are only SQL statements, which can therefore only affect other tables. The best idea we could come up with was to have the triggers modify a table, and have a process in a quick loop watching this table. (This isn't as bad as it sounds. We do this even now in V6, only we watch the audit trail! A separate server does all the watching and audit management, and dispatches appropriate events to its clients. I'll probably be rewriting this to use triggers pretty soon.)

There is a product "Open Gateway" which sounds interesting. It's an oracle interface which will allow you to make just about anything look like a table (from what I can gather from the very limited information I've been able to elicit from Oracle.) It's intended for doing things like interfacing to other databases, flat files, filesystems, etc.; but we'd also like to use it to 1) make a better database monitor system, and 2) maybe to interface to our measurement and control hardware.

Unfortunately, getting information from Oracle about this is like pulling teeth from a gear. I don't think they have any idea when this will be released.

I've also come across interesting references to a "standard" transaction interface/protocol/something, which one might be able to tap into. Again, info is pretty scarce.

-- 
Frederick G. M. Roeber | CERN -- European Center for Nuclear Research
e-mail: roeber_at_cern.ch or roeber_at_caltech.edu | work: +41 22 767 31 80
r-mail: CERN/PPE, 1211 Geneva 23, Switzerland | home: +33 50 20 82 99
--  
"Sorry, baby, I can't take you to the pizza joint tonight, I've got to go
back to the lab and split the atom." -- Ayn Rand, "What is Romanticism?"