Hi Yalim, Thanks. Do you know whether Gitora stores version information in the database itself?
Kind regards, Gian On Thursday, April 2, 2015 at 5:18:09 PM UTC+2, Yalım K. Gerger wrote: > > Hi Gian, > > Yes I suppose so. You can commit packages to git using Gitora. At that > point each package spec and body has a commit code in Git and the ball is > in your court to do whatever you want to do with them. > > Kind Regards, > Yalim > > > > On 02 Apr 2015, at 16:57, Gian <[email protected] <javascript:>> wrote: > > Good afternoon Yalim & Lukas, > > Thanks for chiming in ;) > > A brief description of our case...in our project we are relying heavily on > PL/SQL db objects, it is basically the business layer on which the higher > layers hook on. In this db layer the stored procedures form the interface > and tables/views are hidden. > > What I'm looking for is a solution that allow us to version database > objects and more specifically packages but not necessarily tables/views. If > the version number is retrievable by our automated continuous > build/deployment we would then know when to trigger the generation of jOOQ > code. > > Do you think this is possible? > > Thank you, kind regards, > > Gian > > > On Thursday, April 2, 2015 at 3:42:56 PM UTC+2, [email protected] wrote: > >> Hi Gian, >> >> Gitora is a free tool that helps developers bridge the Oracle Database >> and Git. You are welcomed to try it for your use case. Gitora is >> specifically designed to handle PL/SQL and it can manage triggers as well. >> >> Please let me know if you have any questions, and I'd be happy to help. >> >> Kind Regards, >> Yalim >> >> On Thursday, April 2, 2015 at 1:00:48 PM UTC+3, Gian wrote: >>> >>> Good morning all, >>> >>> In order to better manage and streamline the introduction of jOOQ into >>> our project >>> we're thinking of automated management of version control. This would >>> allow us >>> to 'hand-shake' and trigger the generation of jOOQ objects only at the >>> right moment. >>> >>> There are various tools such as dbdeploy and flywaydb allowing this >>> version management, >>> but they are not so strong in managing stored (PL/SQL) procedures >>> versions. The >>> latter is the most important use case in our case. >>> >>> Do you have experience with this and would you go for an out of the box >>> solution? >>> >>> Personally I'm inclined to build a custom simple solution... >>> >>> Best regards, >>> >>> Gian >>> >> -- 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.
