"genman" wrote : | But instead of writing code, one thing you could consider is simply adding a update timestamp column to the cache loader's table, which is populated through a trigger. Then a background process run by your DBA could cull the data as necessary. |
With the fixes Manick have done, now I can subclass JDBCCacheloader, and introduced a timestamp in: TimestampedJDBCCacheLoader.populatePreparedStatementForInsert | TimestampedJDBCCacheLoader.updateNode | | and also: | TimestampedJDBCCacheLoaderConfig.constructCreateTableDDL | TimestampedJDBCCacheLoaderConfig.constructUpdateNodeSql | TimestampedJDBCCacheLoaderConfig.constructInsertNodeSql | | This modifications add a timestamp column, and set timestamp value in every insert/update in the database and no need to cal the DBA guy to insert a trigger. | | We are developing a product, we are a group of 5 developers, with different databases (mysql, oracle) as target for our application, so this solution seems easier for us. No need to know on target database peculiarities. | | Probably to do a more complex mapping as you suggest, needs more programming on the JDBCCacheLoader subclass, but sometimes can be useful, as per when the client you deploy the app in, wants, no matter how, to have the dba guy tunning the DB, and wanting to know what goes into the DB. You know they aren`t very eager to rely on blobs. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223928#4223928 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223928 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
