Hi Shyam, This would take quite a bit of time and we currently don't want to formally support the jOOQ-meta API for custom extension as it is not a very stable API. So, if you would really like to play around, why not give it a shot on your side and and we'll help with any issues that may arise.
Best Regards, Lukas 2014-02-07 10:16 GMT+01:00 Sha <[email protected]>: > Hi Lukas, > > I would be very thankful to you, if shared how to implement it. > > Thank you. > ~Shyam > > On Friday, February 7, 2014 2:09:46 PM UTC+5:30, Lukas Eder wrote: >> >> >> >> 2014-02-07 7:53 GMT+01:00 Sha <[email protected]>: >> >> Thank you so much for your details reply Lukas. >>> Please find my comments below. >>> >>> >>> On Thursday, February 6, 2014 11:57:30 PM UTC+5:30, Lukas Eder wrote: >>>> >>>> Hi Shyam, >>>> >>>> Finding the "correct" procedure / approach to integrate a source code >>>> generator into your development and build processes is a challenging task >>>> and it depends on your existing development processes, team size, database >>>> setup and much more. >>>> >>>> Some people prefer to have a single "master database" from which they >>>> generate source code. Others prefer to have several "developer databases" >>>> from which each developer generates their own local dev-version of the >>>> generated source code. >>>> >>> We use our own local dev-versions >>> >>>> >>>> Then, you should ask yourself if you want to put generated code under >>>> source control or if it should be generated on the fly by your build. Both >>>> are viable approaches, each with their own advantages and disadvantages. >>>> >>> >>> We want to generate on the fly. >>> >>>> You can even implement your own "Database" (from jOOQ-meta) and provide >>>> jOOQ's code generator with your own database meta information, e.g. from an >>>> XML file. This may be useful if you work with an ERD design program or a >>>> database modeler. Future versions of jOOQ may actually provide such >>>> "Database" implementations >>>> >>> >>> How to implement our own "Database" (from jOOQ-meta) and provide jOOQ's >>> code generator with your own database meta information ? Where can I find >>> more details of such implementation ? any url or docs ? >>> >> >> Currently, this is an undocumented feature. See also the following >> section of the manual, which includes a disclaimer with respect to semantic >> versioning in jOOQ-meta: >> http://www.jooq.org/doc/3.2/manual/getting-started/semantic-versioning/ >> >> jOOQ-codegen and jOOQ-meta >> While a reasonable amount of care is spent to maintain these two modules >> under the rules of semantic versioning, it may well be that minor releases >> introduce backwards-incompatible changes. This will be announced in the >> respective release notes and should be the exception. >> >> However, it should be quite straight-forward to implement your own >> Database if this is really a useful approach to your use-case. >> >> Regards, >> 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.
