Will report what have we done ... Otherwise, this j00q of yours is nevertheless the far most usable library I've seen ... Congrats for nice work!
On Monday, November 5, 2012 1:23:35 PM UTC+1, Lukas Eder wrote: > > Hello Marko, > > From what I understand, you would probably want to add some sort of > trigger to your database, which invokes a database notification mechanism. > I have recently given an answer to this Stack Overflow question, regarding > a similar topic: > http://stackoverflow.com/a/12619031/521799 > > From what I know, these databases support such notification features: > > Oracle: > > > - The > DBMS_ALERT<http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_alert.htm> > is > a simple means for such notification > - Oracle AQ / Oracle > Streams<http://www.oracle.com/technetwork/database/information-management/streams-fov-11g-134280.pdf> > provide > more sophisticated queue mechanisms > > Postgres: > > > - The NOTIFY<http://www.postgresql.org/docs/9.2/static/sql-notify.html> > statement > is a simple means for such notification > > I doubt that in MySQL, you will be able to implement something similar. > Neither does jOOQ have something like that built-in. If you want to heavily > rely on such notification / caching mechanisms, you may want to look into > EhCache or JBossCache or any similar product, which allows to synchronise > caching state among your 5 nodes. But then again, this will have to be done > outside of jOOQ. > > I'd be curious to hear about your further steps / decisions, as this is > indeed an interesting problem. > > Cheers > Lukas >
