On Sun, Feb 3, 2013 at 3:07 AM, Lukas Eder <[email protected]> wrote:
> Hello and thank you for your interest in jOOQ > > > I've done a review of jOOQ already, and am fairly pleased with what I > see, > > - Support of Postgres + PostGIS > > Unfortunately, that's not true. The PostGIS extension isn't really > well supported by jOOQ. This has been on the roadmap for a while now: > https://github.com/jOOQ/jOOQ/issues/982 > > > - Support new dynamic query options > > What are these, according to you? > Nothing crazy, just the ability to append conditions, the SelectSelectStep object looks like it works for all the needs I have. > > > - Cleaner, more obvious DB API > > - Support for functions (PostGIS has a lot) > > Yes. > > > - Support for PGobject (and thus PGhstore, PGgeometry, and PGgeometryLW) > > They *might* work, but jOOQ doesn't guarantee anything > Well, selects and inserts (which is the bulk of what I do) worked for all these object types without any weird binding issues. > > > 1. I was trying to use a PostGIS routine st_intersects(geom1, geom2) -> > > boolean, but jOOQ tries to cast the inputs: > > Unfortunately, as I said, with jOOQ 2.6 you will probably not be able > to properly use PostGIS. It will probably work as long as you avoid > variable binding of PG* objects, though. > Well I'm used to having to implement all of this in raw JDBC, are there any facilities in jOOQ to extend, or what not? I found these: http://www.jooq.org/doc/2.6/manual/sql-execution/fetching/data-type-conversion/ http://www.jooq.org/doc/2.6/manual/code-generation/custom-data-types/ So I see how the converters can work for tables easily enough - is there something similar for routines? > > 2. WIth this refactoring of the Java, I'm trying to figure out how I > could > > implement table partitioning - suggestions? > > > > Table partitioning in Postgres is implemented via table inheritance. > > Partitioning tables in Postgres can make working with the data more > > complicated and slower though. To avoid some of the slowdown I plan to > use > > jOOQ's ability to dynamically build queries, assigning inserts, updates, > and > > deletes to the correct table(s) avoiding using triggers and other > Postgres > > magic functions - I'm wondering if you have any suggestions on this... > > Postgres' table inheritance feature currently isn't supported > explicitly, either. This was discussed a long time ago on the user > group: > https://groups.google.com/d/topic/jooq-user/YuTp9-5K9fs/discussion > > I haven't followed up on that discussion yet. In order to see how > suggestions could be made, could you explain a bit more about your > partitioning use case? This sums it up pretty well - http://www.postgresql.org/docs/9.1/static/ddl-partitioning.html The difference between the above example and what I'm trying to implement is the insert logic will be done in the Java code and not by a trigger. I was looking for suggestions on how best to use jOOQ for this - I was considering a DAO implementation, but I'm not sure how the DAO interfaces tie to jOOQ (are they just a convence layer?) and the interface is so very tightly bound to the record and table interfaces of jOOQ it looks like I would have to drop all the type safety. Pete -- 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/groups/opt_out.
