Hi Peter, What would be the added value of these types? To me, java.sql.Types.OTHER >> is the most appropriate JDBC type for what you call unresolved / >> userdefined: >> http://docs.oracle.com/javase/**7/docs/api/java/sql/Types.**html#OTHER<http://docs.oracle.com/javase/7/docs/api/java/sql/Types.html#OTHER> >> > > Well, then OTHER works for USERDEFINED, I was really thinking of ways to > avoid tripping over the unresolved type issue in #2007 on the Java side. > Only thinking aloud here, not trying to say anything. >
I see. Hmm, I'm not sure if it would change something, to have two org.jooq.DataTypes that bind to java.lang.Object. I guess there would be some cases, where it will be hard to decide, whether Object should map to OTHER, or UNRESOLVED > I'd love to be able to compile and test out this change - see where that > takes me. > I have pulled the code down, and read through some of the info for > compiling jOOQ from source, but I'm running into problems. > > I admittedly am not an Eclipse guy, so after tripping over that a lot, I > tried Netbeans and think things are "compiling", except when I now run the > generator tool > > Feb 25, 2013 12:07:50 PM org.jooq.tools.JooqLogger info > INFO: relations : true > Feb 25, 2013 12:07:50 PM org.jooq.tools.JooqLogger info > INFO: global references : true > Feb 25, 2013 12:07:50 PM org.jooq.tools.JooqLogger info > INFO: ---------------------------------------------------------- > Feb 25, 2013 12:07:50 PM org.jooq.tools.JooqLogger info > INFO: Emptying : > /Users/petri/Development/test4-jooq-gis/src/gis/generated > Exception in thread "main" java.lang.NoSuchMethodError: > org.jooq.impl.Factory.val(Ljava/lang/Object;)Lorg/jooq/Field; > at org.jooq.impl.Limit.<init>(Limit.java:61) > at org.jooq.impl.SelectQueryImpl.<init>(SelectQueryImpl.java:140) > at org.jooq.impl.SelectQueryImpl.<init>(SelectQueryImpl.java:121) > at org.jooq.impl.SelectImpl.<init>(SelectImpl.java:144) > at org.jooq.impl.SelectImpl.<init>(SelectImpl.java:140) > at org.jooq.impl.Factory.select(Factory.java:248) > at org.jooq.impl.Executor.select(Executor.java:1765) > at org.jooq.impl.Executor.select(Executor.java:1802) > at > org.jooq.util.postgres.PostgresDatabase.getSchemata0(PostgresDatabase.java:220) > at org.jooq.util.AbstractDatabase.getSchemata(AbstractDatabase.java:148) > at org.jooq.util.JavaGenerator.generate(JavaGenerator.java:168) > at org.jooq.util.GenerationTool.main(GenerationTool.java:257) > at org.jooq.util.GenerationTool.main(GenerationTool.java:103) > Java Result: 1 > > > > Maybe this is caused by my using NB instead, I'm not sure what NB is doing > when it compiles the Mavan project or what targets its using. > Looks to me like some old artefacts are lying around...? Factory.val used to return org.jooq.Field, whereas in jOOQ 3.0, it now returns org.jooq.Param. I'm not sure how this could be caused, though... Calling "mvn package" from the command line in the project / sub-project > directories is only kind of successful. > What do you mean by "kind of successful" ? -- 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.
