Hi Ryan, 2014-05-28 15:46 GMT+02:00 Ryan How <[email protected]>:
> Cheers :). > > I'll have a go and see how it goes! > > It's late and I'm well overdue for sleep, so probably not thinking clearly! > > I think the SPI basically seems to do a lot of work that we implemented in > another application, so I can probably take a similar approach, just that > you've done the hard bit :) > > I'll post anything back here, hopefully in a bit less rushed and more > sensical manner (Is that even a word?) :) > No worries ;-) Looking forward to your insights. Actually, of course we do have an example use for VisitListeners. Here are the integration tests: https://github.com/jOOQ/jOOQ/blob/af7a7c504c08fcd4ecb10c9ca4091a7cff930fb8/jOOQ-test/src/test/java/org/jooq/test/all/testcases/VisitListenerTests.java testVisitListenerOnSELECT testVisitListenerOnDML These tests add an additional author_id = 1 predicate to SELECT, UPDATE, DELETE statements. The first one checks if the VisitListener correctly transforms all sorts of statements, e.g. derived tables, aliased column references (e.g. b.author_id instead of t_book.author_id), etc. testVisitListenerFailOnMissingWhere This test fails all SELECT, UPDATE, DELETE statements that don't have a WHERE clause The blanked out sections are Oracle-specific code to transform INSERT statements into INSERT INTO (SELECT * FROM t_author WHERE author_id = 1 WITH CHECK OPTION) (...) VALUES (...) -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
