Re: Tracking Data Model changes

Thank you all for your valuable inputs. We have added the markdown file to trunk with all the data model changes from Release 9 to Release 17 at R1818765 and it will soon be part of the next release. The page is also added as child page to wiki page Revisions Requiring Data Migration - upgrade

Re: Tracking Data Model changes

Hello all, I have created a ticket here . I will be adding information about data model changes between OFBiz.9 to OFBiz.17.11 in the initial file. As commented on the ticket, The file will have the format: Entity Changes: Here we will have

Re: Tracking Data Model changes

+1 for tracking datamodel changes together with data migration scripts In our customer projects, we track every change in a simple text file in the source code repository. It contains description of the changes, references to issues or requirement documentation and SQL scripts for migrations.

Re: Tracking Data Model changes

That would be a much effective solution. As far as https://cwiki.apache.org/confluence/display/OFBIZ/ Revisions+Requiring+Data+Migration+-+upgrade+ofbiz page is concerned I find it quite absurd that we provide information based upon only revisions while users deal with releases. Though it would

Re: Tracking Data Model changes

Hi Aditya, One way we could use and is already used for the Gradle and Birt Flexible documentation in wiki is to create README.md files, uses Pandoc to generate a HTML file from it in tools\wiki-files and import this file in wiki using the HTML import macro. Doing  so we follow both way you

Re: Tracking Data Model changes

I see two ways to do that 1. A page maintained on Confluence where all the data model changes are updated. Here, we can have a page maintained for the upcoming release when the release is out we make it sub child titled with the release name. 2. A file is maintained in ofbiz-framework code base

Re: Tracking Data Model changes

+1 for the documentation of database changes. We alreadyy do this for customer projects, along with (database specific) data migration scripts. I'm not sure if we can afford to provide sophisticated additional tool support which is maintained continiously? As a conclusion, I think we

Re: Tracking Data Model changes

Groovy scripts are also great and can do the job. To comment on the "advantage" of something like flyway or liquibase I can try to list some: - The scripts might get too big or complex to accommodate different databases and platforms. - Out of the box, these solutions are database independent -

Re: Tracking Data Model changes

I'm in favor to tracking the different migration but at this time I didn't see the advantage to use flyway or other instead of manage easily by ofbiz throw groovy script. I'm available to help for design or create a POC do realize it because many time in the past (and currently ow) I want to

Re: Tracking Data Model changes

Le 31/08/2017 à 12:32, Taher Alkhateeb a écrit : I would personally prefer to not go any earlier than 13, or preferably just 16 to trunk, which means we design this solution for the future, not necessarily the past. +1 Jacques

Re: Tracking Data Model changes

Hi Ashish, With respect to Jacques' question, I kind of already answered in that it is not only documentation but also automation. Now with respect to which releases to incorporate, it really depends on what the community decides. I would personally prefer to not go any earlier than 13, or

Re: Tracking Data Model changes

It's a good idea +1. Best regards, Pranay Pandey www.hotwaxsystems.com www.hotwax.co On Wed, Aug 30, 2017 at 6:53 PM, Aditya Sharma < aditya.sha...@hotwaxsystems.com> wrote: > Hello everyone, > > For one of my assignments, I need to find out entity changes that took > place between an older

Re: Tracking Data Model changes

+1, Taher. I will wait for your comment on Jacques question, we already have a document but I think the automated script that can be implemented here. Liquidbase and flyway seem to be promising solutions! One question always comes to my mind: Can we say that automated scripts will support the

Re: Tracking Data Model changes

Hi Taher, You mean something more than https://cwiki.apache.org/confluence/display/OFBIZ/Revisions+Requiring+Data+Migration+-+upgrade+ofbiz ? If yes, why? Thanks Jacques Le 30/08/2017 à 16:24, Taher Alkhateeb a écrit : Good idea! Why not take it a step further, and write data migration

Re: Tracking Data Model changes

Good idea! Why not take it a step further, and write data migration scripts? They will serve two purposes in one: 1) document changes 2) automate upgrades. You can experiment with solutions like liquibase or flyway On Aug 30, 2017 4:23 PM, "Aditya Sharma" wrote:

Re: Tracking Data Model changes

+1 Great Idea Aditya !!! On Wed, Aug 30, 2017 at 7:28 PM, Aishwary Shrivastava < aishwary.shrivast...@hotwaxsystems.com> wrote: > Indeed it's a great idea, Aditya!! > +1 > > On Wed, Aug 30, 2017 at 7:06 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > +1 clearly > > > > Jacques

Re: Tracking Data Model changes

Indeed it's a great idea, Aditya!! +1 On Wed, Aug 30, 2017 at 7:06 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > +1 clearly > > Jacques > > > > Le 30/08/2017 à 15:23, Aditya Sharma a écrit : > >> Hello everyone, >> >> For one of my assignments, I need to find out entity changes

Re: Tracking Data Model changes

+1 clearly Jacques Le 30/08/2017 à 15:23, Aditya Sharma a écrit : Hello everyone, For one of my assignments, I need to find out entity changes that took place between an older release and the latest release. One of the solutions that came up was comparing the database using MySQL Workbench

Tracking Data Model changes

Hello everyone, For one of my assignments, I need to find out entity changes that took place between an older release and the latest release. One of the solutions that came up was comparing the database using MySQL Workbench or some other utility. I found around 60+ new entity changes and a lot