Hi John, how do you (and everyone else) feel about including this in the main repo after polishing?
I'm working with Hugi here on a project and would like to continue using this style of migrations because our entire environment is geared towards it. I'd love for this to be in the main cayenne repo so we can submit our improvements. Maik > Am 09.02.2017 um 15:59 schrieb John Huss <[email protected]>: > > It's current except for a single small change. I seem to have lost the > push url, so I need to get it working again to update it. But it would be > fine for playing with as is. > > On Thu, Feb 9, 2017 at 9:45 AM Hugi Thordarson <[email protected]> wrote: > >> Hi John, >> that’s very interesting. Is your current work public or is the most recent >> public work in the SVN-repo I mentioned? >> >> Cheers, >> - hugi >> >> >>> On 9. feb. 2017, at 15:36, John Huss <[email protected]> wrote: >>> >>> I'm developing and using cayenne-migrations. It works fine for me and >> has a >>> very similar approach to ERXMigrations. I don't think others are using >> it >>> though. It has the advantage of being able to auto-generate the >> migration >>> code from your cayenne model (DataMap), where I think the others require >>> hand coding. On the other hand, sometimes having all pure SQL statements >>> instead of mostly java code is useful. Good luck! >>> >>> John >>> >>> On Thu, Feb 9, 2017 at 9:15 AM Michael Gentry <[email protected]> >> wrote: >>> >>>> Hi Hugi, >>>> >>>> We manage schema changes outside of Cayenne using Flyway (could also use >>>> Liquibase). Any schema changes we make are updated by hand in Cayenne >>>> Modeler. This works fairly well for us and fits in with our automated >>>> builds/etc. Perhaps not the answer you were looking for, though! >>>> >>>> mrg >>>> >>>> >>>> On Thu, Feb 9, 2017 at 9:21 AM, Hugi Thordarson <[email protected]> >> wrote: >>>> >>>>> Hi all. >>>>> In EOF/WOnder we have the most swesome ERXMigrations to manage changes >> in >>>>> the data model between versions, i.e. upgrades of the schema (and >>>>> downgrades, if applicable). >>>>> >>>>> I see that some years ago there was discussion of an API to handle this >>>> in >>>>> Cayenne ( http://svn.apache.org/repos/asf/cayenne/sandbox/cayenne- >>>>> migrations/ ). but how’s the situation today? Is there something in/for >>>>> Cayenne to do this, and if not, what tools are people using to manage >>>>> versioning of their DB schemas? >>>>> >>>>> Cheers, >>>>> - hugi >>>> >> >>
