Your use-case sounds perfect for jOOQ's VisitListeners: http://www.jooq.org/doc/latest/manual/sql-building/queryparts/custom-sql-transformation
I've just recently written a blog post about how to implement row-level security with jOOQ: http://blog.jooq.org/2015/06/17/implementing-client-side-row-level-security-with-jooq And Aakash, a jOOQ user has just recently written his own blog post about a similar use-case: http://aakashjapi.com/caching-with-jooq-and-redis Let me know if this is helpful for now. If you want to go down that path, I'll be very happy to provide assistance with any concrete questions that you may have. Cheers Lukas 2015-07-01 20:24 GMT+02:00 Eduardo Ramos Ibáñez <[email protected]>: > Hi, > > I was wondering wether it's possible to extract fields from a select, but > without being limited to their alias? > If I use select.fields() I get the alias of the fields, but I cannot > access the underlying expression of each one. > > This would be useful for extracting selected expressions from an unknown > select and adding filters based on them (without doing a subselect, for > which alias fields are fine). > > As a workaround, I guess I can always keep a separate collection of fields > and provide it with the select, but I would like to avoid doing that if > possible. > > Thank you > > -- > 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. > -- 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.
