Hmm, while fixing #2864, I've noticed that the Oracle 11g check in OracleRoutineDefinition might not be correct, either. I've fixed this also for jOOQ 3.3. and 3.2.2: https://github.com/jOOQ/jOOQ/issues/2866
Cheers Lukas 2013/11/26 Lukas Eder <[email protected]> > Hi Sergey, > > Thanks for reporting. While jOOQ does not officially support Oracle 9i, > the ALL_MVIEW_COMMENTS issue should be easy to fix. I'll schedule a fix for > jOOQ 3.3 and 3.2.2: > https://github.com/jOOQ/jOOQ/issues/2864 > > The ALL_PROCEDURES issue has been fixed in jOOQ 3.2.0: > https://github.com/jOOQ/jOOQ/issues/2584 > > Cheers > Lukas > > > 2013/11/25 Sergey Epik <[email protected]> > >> Hello, >> >> we faced the same problems with Oracle 9.2: >> - it does not have view SYS.ALL_MVIEW_COMMENTS, >> - view SYS.ALL_PROCEDURES does not have column OBJECT_TYPE >> So, jooq 3.0.1 could not generate all artifacts for schema on Oracle 9.2. >> >> >> On Fri, Jun 21, 2013 at 9:46 PM, Lukas Eder <[email protected]> wrote: >> >>> Hi Philippe, >>> >>> I'm sorry, this mail got lost in my inbox... >>> >>> >>> 2013/6/6 <[email protected]> >>> >>>> Hello Lukas, >>>> I'm still there. >>>> I have starded to read as many things as I can to understand jOOQ >>>> (official >>>> documentation, some very interesting discussions on the user group >>>> about pro >>>> and cons for some design decisions, ...). >>>> I'm impatient to have a view of the "BNF" used to design the DSL. >>>> >>> >>> Yes, I'm a bit impatient as well. However, I haven't had time to fully >>> delve into this area in a way for it to be ready to be published in jOOQ >>> 3.1... >>> >>> >>>> I'm currently very busy, professionaly and privately ... but I'm still >>>> very >>>> interested in participating in a manner or an other to your project : >>>> perhaps on >>>> the parsing of sql text to construct jOOQ DSL objects. For sure, it's a >>>> big >>>> challenge and, in a certain point a view, more complex than >>>> constraining SQL in >>>> java by the jOOQ DSL. But, it's exciting, isn't it ? :D >>>> >>> >>> Yes, it is exciting! However, at first, this only serves for >>> documentation purposes, when we'll generate API -> BNF -> Railroad diagrams >>> with Christopher's RRDiagram tool: >>> https://github.com/Chrriis/RRDiagram >>> >>> Writing a parser for jOOQ SQL is another story. You could even write a >>> JDBC driver, if you want (and dare) ;-) >>> >>> >>>> Concerning the problem with codegen, I really improved the >>>> OracleDatabase class, >>>> by using an auto detection of the database capabilities (testing for >>>> existence >>>> of certain views or columns as in OracleRoutineDefinition), and my >>>> version is >>>> compatible with all three versions of Oracle (9, 10 and 11). No older >>>> version >>>> to test :D >>>> If you want, I can send you the code (after readaptation for the jOOQ >>>> java >>>> package hierarchy - I have coded the improved class in my own package). >>>> Just >>>> tell me ! >>>> >>> >>> Sure! You can send any code snippets to the user group, or provide a >>> pull request if you prefer >>> >>> Cheers >>> Lukas >>> >>> >>>> >>>> Friendly >>>> >>>> Philippe >>>> >>>> >>>> Selon Lukas Eder <[email protected]>: >>>> >>>> >>>> > Hi Philippe, >>>> > >>>> > Just checking back with you... >>>> > >>>> > 2013/5/13 Philippe Colin <[email protected]> >>>> > >>>> > > >>>> > > >>>> > > Le mercredi 8 mai 2013 19:49:13 UTC+2, Lukas Eder a écrit : >>>> > >> >>>> > >> >>>> > >> 2013/5/7 Philippe Colin <[email protected]> >>>> > >> >>>> > >>> Ok Lukas, the workaround with JDBCDatabase did its job ! >>>> > >>> jooq-codegen had generated the things I need to continue my work >>>> :-) >>>> > >>> >>>> > >> >>>> > >> Great, good to know. >>>> > >> >>>> > >> >>>> > >>> SQL 99 doesn't know VARCHAR2 and create Object Fields, but it's >>>> not a >>>> > >>> problem. >>>> > >>> >>>> > >> >>>> > >> Hmm, yes that is a problem, which should be fixed. I have >>>> registered >>>> > >> #2445 for this. Thanks for reporting. >>>> > >> >>>> > >>>> https://github.com/jOOQ/jOOQ/**issues/2445< >>>> https://github.com/jOOQ/jOOQ/issues/2445> >>>> >>>> > >> >>>> > >> >>>> > > >>>> > >> I guess that with #2310, the SQLDialect could be auto-detected >>>> from the >>>> > >> JDBC connection: >>>> > >> >>>> > >>>> https://github.com/jOOQ/jOOQ/**issues/2310< >>>> https://github.com/jOOQ/jOOQ/issues/2310> >>>> >>>> > >> >>>> > >> >>>> > >>> I think I will try, if I hade some time, to create my own >>>> > >>> OraclePriorTo102Database.java dialect class and to see : >>>> > >>> - first, if I'm able to do that, >>>> > >>> - second, if there are no other problems for Oracle versions >>>> prior to >>>> > >>> 10.2 in the original OracleDatabase dialect class. >>>> > >>> >>>> > >> >>>> > >> That would be greatly appreciated. On the other hand, you might >>>> also >>>> > >> consider detecting the Oracle version dynamically. This is already >>>> done >>>> > >> today to distinguish 10g and 11g: >>>> > >> https://github.com/jOOQ/jOOQ/**blob/master/jOOQ-meta/src/** >>>> > >> >>>> > >>>> main/java/org/jooq/util/**oracle/**OracleRoutineDefinition.java#**L143< >>>> https://github.com/jOOQ/jOOQ/blob/master/jOOQ-meta/src/main/java/org/jooq/util/oracle/OracleRoutineDefinition.java#L143 >>>> > >>>> >>>> > >> >>>> > >> Of course, this could be improved, too, so I'm very open to >>>> suggestions. >>>> > >> >>>> > > >>>> > > In fact, I have improved the code of the OracleDatabase class and >>>> put it >>>> > > in my own java package (and then reference it in the classpath of >>>> > > jooq-codegen and in the xml file). >>>> > > I did something like it has been done in OracleRoutineDefinition >>>> (before >>>> > > you've suggested it, really :-), for I thought it was an elegant >>>> way to >>>> > > code). It was ok with the Oracle 10.1 database ! >>>> > > But then, I had another problem with an Oracle 9 database (a legacy >>>> > > application which doesn't want to die ... I need to access one >>>> Oracle 10.1 >>>> > > databases, one Oracle 9 database and one MS SQL Server -I"m not >>>> sure of its >>>> > > version- in my use-case). >>>> > > The ALL_MVIEW_COMMENTS view is not present in Oracle 9. I have to >>>> do some >>>> > > researches in Oracle documentation to find the good view to use, if >>>> it >>>> > > exists ... >>>> > > For the moment, I have no time to install Eclipse and configure all >>>> the >>>> > > things needed to do a good job for the jOOQ project, but I could >>>> send you >>>> > > the "improved" OracleDatabase.java code ... >>>> > > >>>> > > >>>> > >> >>>> > >>> I'm very interested to participate in a manner or an other to this >>>> > >>> pretty good project. >>>> > >>> Please, let me know how I could do that ... >>>> > >>> >>>> > >> >>>> > >> Any contribution is greatly appreciated. Some information can be >>>> found >>>> > >> here: >>>> > >> http://www.jooq.org/community.**php < >>>> http://www.jooq.org/community.php> >>>> >>>> > >> >>>> > >> Note, there is a dedicated milestone for user contribution >>>> candidates >>>> > >> here: >>>> > >> >>>> > >>>> https://github.com/jOOQ/jOOQ/**issues?milestone=20< >>>> https://github.com/jOOQ/jOOQ/issues?milestone=20> >>>> >>>> > >> >>>> > >> Not all tasks are equially simple, though. What kind of work would >>>> you be >>>> > >> most interested in? >>>> > >> >>>> > > >>>> > > That's a good question :D. >>>> > > I have to read more about the jOOQ project, to understand the >>>> milestones >>>> > > and goals. I think I will be more interested by improvements or new >>>> > > features, but I have to read more ... >>>> > > I'll stay you informed as soon as possible ;-) >>>> > > >>>> > >>>> > ... were you able to make some progress with your attempts of fixing >>>> Oracle >>>> > 10g1 support? Is there anything I can help you with? >>>> > >>>> > 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/groups/opt_out. >>> >>> >>> >> >> -- >> 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. >> > > -- 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.
