We've got a fairly typical triggered publication JDBC driver
configuration. One problem we have is that from time to time, the
source system goes through some processing that sends several thousand
modifies (event type 6) to the event log table.

The modifies are appropriate, so we don't want to drop them, but
creates (event type = 5) are more important to us, so those end up
getting queued behind tons of modifies.

Is there anyway to prioritize how the JDBC driver selects records from
the event log table? Something like "select * from event log order by
event_type" would work.

It seems that the event log table queries are hard coded into the JDBC
shim.

We don't want to setup separate drivers for adds & modifies or make
massive changes to existing drivers.

Any ideas?

thanks!

Eric


--
ekuzmack
------------------------------------------------------------------------
ekuzmack's Profile: http://forums.novell.com/member.php?userid=5487
View this thread: http://forums.novell.com/showthread.php?t=333650