Hi Devin, Here's the promised follow-up
2016-05-25 20:28 GMT+02:00 Devin Austin <[email protected]>: > 3. I thought it might be easier to just extend the DAOImpl class like you > suggested, but I'm still left with figuring out how to shoe-horn in sorting > and such, so I don't think that's a viable route at this point. > You have to decide whether you want to expose the jOOQ API to consumers of your services (e.g. Field, SortField, Condition, etc.) or if you want to implement your own criteria API. From then on it's just yak shaving. > I would, however, be more than happy to help contribute sorting and > limiting conditions if that's on the future TODO list. > Yes it is. I cannot seem to find the issue on GitHub right now, but it might be a nice feature. The only question is the same as the one above. Should we really expose the jOOQ API? > 4. A slight tangent, but looking at my code I think it would be nicer to > have an interface the lays out the CRUD contract, gets implemented in a > CRUD base class, and then subclassed as needed. My hope would be to make > my database CRUD a good deal more encapsulated and lighter weight, and > allow me to have things like a cache service that's still a service but > completely unrelated to the database CRUD operations. I'm probably just > thinking out loud, but if that makes any of this simpler, please let me > know your thoughts. > Thus far, caching has been out of scope for jOOQ, except perhaps for result set caching as displayed in this blog post: http://aakashjapi.com/caching-with-jooq-and-redis I'm always open for discussion though. What specific use-cases did you have in mind? > I am certainly not adverse to doing something else for my mapping code. I > really just need to have the GALLERIES.COVER_PHOTO get set to either the > value in the database or the default cover photo, which I suppose I could > just set by default when inserting the record, so there's a value for that > column in the database. > How about implementing that using either a trigger, or the DDL "DEFAULT" clause? If you want to implement that on the jOOQ layer, the RecordListener SPI might be interesting to you, given that you intend to implement a CRUD layer anyway. Cheers, Lukas -- 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.
