This cannot be achieved with
JDBC, however, you can fiddle with triggers for reverse notification. I encountered this issue when writing the 'JDBC Adapter for IBM Tivoli Risk Manager'. Your best case is to abstract the busy/wait so that it appears to clients as if they are registering for notification, then write implementations to suit - each with their own trade-offs.