Forward patching with SqlCL Liquibase changelogs linking to actual ddl-files

Paavo

While waiting SqlCL to be have more recent Liquibase supporting linking sql / ddl-files in the changelog-files came to conclusion that it would be very elegant to have Datamodeler to do the disciplined merge ddl's.

So shortly:

1.) make change to design

2.) "synchronize data dictionary with model"

3.) DDL Preview with option to file per object (matching the genobject).

4.) Save to sqlcl liquibase Release-target directory with disciplined runorder

5.) Edit the changesets per object in changelogs to include new patch-files (4.)

6.) Add all files to version control, commit and push

7.) Launch sqlcl to patch

So the target directory has e.g. something like this:

changelogs
I...emp.xml
I...dept.xml
scripts
I...Release202111
    I..00_emp-patch-ddl-from-DModeler.sql
    I..01_dept-patch-ddl-from-DModeler.sql
I...Release202112
I...Release202201

Philip Stoyanov-Oracle

@https://community.oracle.com/tech/developers/profile/Paavo

Can you work with Oracle support to log ER

Paavo

@Philip Stoyanov-Oracle or do you have "community requests" type of application, so more "talented" LB and DM users could then contribute to comments about how to do it?

I can submit it to support, but it will take time to massage it to such form that it is easier to adapt..

Basically I forecast 2 hard problems to be solved in DM merge button ddl-preview output generation:

• split the ddl's per object, check if it is doable to with subdirectories
• decide run order
• create lb changesets for the release
• link the DM change requests per object or the whole model with the generated ddl's (this is the checked out branch == release xyz assumption). So this expects that the DM change requests can be linked to some release / branch or so? This part is a bit blurry how to do.
• Have a Release Note to the design, so it can show the changed objects/closed CR's per release?
• and of course then sqlcl should be able to use those changeset patchfiles - so the best practice includes this step too...
• and get wild and rethink the release and editionable release information :)

rgrds Paavo

Philip Stoyanov-Oracle

@Paavo discussion can be done here, still it's important to have legal service request through Oracle support

Regards,

Philip

Paavo

https://community.oracle.com/tech/developers/discussion/comment/16821911#Comment_16821911

So ER stands for enhancement request I think, so created this SR 3-28273910951 let me know if this is enough because it refers to this discussion thread and it takes some time and hopefully community contributions from others to find elegant spec. for the idea. Surely you already catched it as-is already :) ..

ps. I tried to look myos for proper way to submit the idea and ended to Doc. 2299828.1 and via that here: https://community.oracle.com/mosc/categories/misplaced-ideas but became very hesitant to add the idea there. About ideation.. I like the apex app for community requests a bit more due its datamodel which has ratings and sort of board to handle the ideas etc.. :)

Philip Stoyanov-Oracle

I like the apex app for community requests a bit more

I don't like it because you cannot see who is behind the idea and to ask to elaborate on some points and to have a real discussion

Paavo

https://community.oracle.com/tech/developers/discussion/comment/16822067#Comment_16822067

Yes, maybe the the apps datamodel requires abit more work in DataModeler, if we are talking about this: https://apexapps.oracle.com/pls/apex/apex_pm/r/ideas/home I think this is the new incarnation of the community requests. I can see my old requests there like this: https://apexapps.oracle.com/pls/apex/apex_pm/r/ideas/details?idea=FR-821

I once were able to download the app "community requests" and then it was a bit lagging behind from Apex releases. The same was for rasadm. Both those required some work to get them working in more recent Apex, but pretty easy fixes. And to extend those with linking e.g. MYOS SR etc. ideation tool links could be perhaps done?

... but this is a bit sidetrack on this DM commands LB towards Editionable DB :)

rgrds Paavo

ps. and yes I understand that the community users dont taste like "real persons" but its hard (at least for me) to change old nicknames towards more "professional" ones without changing the account totally.

Philip Stoyanov-Oracle

That new app looks better. I had in mind this one https://apex.oracle.com/pls/apex/f?p=43135:1:13718701385081:::::

Paavo

https://community.oracle.com/tech/developers/discussion/comment/16822434#Comment_16822434

We are happily diverting a bit from the OP subject, but nevermind . This started to get interesting :)

Yep, it is a separate branch from the original "community requests" apex application. I fiddled with it to UT universal theme and since then been a bit waiting to see if it will be "open sourced" again.

Imho the datamodel in this original design

I can send my dm from the past - in-case that is a good example for LB forward patching etc. fun. I have feeling that the design could benefit about easier management of the Product portfolio and ondemand adding new "alien products" for ballotting new community requests also for products currently not existing at all.

rgrds paavo