<div dir="ltr">It's not really all that silly and from a security standpoint granting a user that normally only does CRUD requests the ability to alter the structure of you database is probably not a good idea.<div><br></div><div>But you're right, there's probably no reason to migrate away from liquibase. If update sql code could be provided or scripts to generate the changes, that would be fine.</div><div><br></div><div>And I currently use the sql_output functionality to generate the sql changelogs but it's a hassle, you have to:</div><div><ul><li>download the right version of the source code (or clone the master and checkout the proper tag)</li><li>modify the pom file in the jpa liquibase code to add the dependencies for your database (cause i know you're not using h2)</li><li>figure out why the "updateSql" task isn't working and update the pom file again with the fix</li></ul><div>I used it to upgrade from 1.3 -> 1.4 but 1.4 -> 1.5 is broke.</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 24, 2015 at 3:35 PM, Scott Rossillo <span dir="ltr"><<a href="mailto:srossillo@smartling.com" target="_blank">srossillo@smartling.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>DBAs don’t like applications modifying the database schema on startup. They want scripts they can review. It’s a bit silly in some ways and I do not think it’s cause for alarm or to move off Liquibase though. Liquibase really simplifies things a lot and it can generate a SQL script to be applied before application startup: <a href="http://www.liquibase.org/documentation/sql_output.html" target="_blank">http://www.liquibase.org/documentation/sql_output.html</a></div><div><br></div><div>As long as Keycloak will run the Java migration code if the DB is updated offline, it should be fine.</div><div><br></div><div>There should be some documentation on upgrading in the user guide. It would be worth documenting the correct way to upgrade, especially if you’re running a cluster or multiple standalone servers sharing a database. I am pretty sure you can’t do a rolling upgrade but someone may try it. ;)</div><br><div>
<div>Scott Rossillo</div><div>Smartling | Senior Software Engineer</div><div><a href="mailto:srossillo@smartling.com" target="_blank">srossillo@smartling.com</a></div><div><br></div><div><a href="https://app.sigstr.com/uc/55e5d41c6533390d03580000" style="color:rgb(0,75,118);font-family:gesta,Arial,Helvetica,sans-serif;font-size:14px;line-height:20px;background-color:rgb(255,255,255);outline:0px!important" target="_blank"><img alt="Latest News + Events" border="0" src="https://app.sigstr.com/uc/55e5d41c6533390d03580000/img" style="border:0px;vertical-align:top;max-width:100%;min-height:auto;width:inherit;color:blue;font-family:Helvetica;font-size:12px"></a><span style="color:rgb(169,169,169);font-family:gesta,Arial,Helvetica,sans-serif;font-size:14px;line-height:20px;background-color:rgb(255,255,255)"></span><div style="color:rgb(169,169,169);font-family:gesta,Arial,Helvetica,sans-serif;font-size:14px;line-height:20px;background-color:rgb(255,255,255)"><a href="http://www.sigstr.com/" style="color:rgb(0,124,194);text-decoration:none;background-color:transparent;outline:0px!important" target="_blank"><img alt="Powered by Sigstr" border="0" src="https://app.sigstr.com/uc/55e5d41c6533390d03580000/watermark" style="border:0px;vertical-align:top;max-width:100%;min-height:auto;width:inherit;color:rgb(99,99,99);font-family:Helvetica;font-size:11px"></a></div></div>
</div>
<br><div><blockquote type="cite"><div><div class="h5"><div>On Sep 24, 2015, at 3:06 PM, Bill Burke <<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>> wrote:</div><br></div></div><div><div><div class="h5">An interesting suggestion from a user<br><br>On 9/24/2015 2:58 PM, Walker, Charles wrote:<br><blockquote type="cite">* move away from liquibase to manage the database schema. it's a nice<br>tool but i haven't ran into many dba's that allow an application to<br>"alter" the database. that meant i just had to go figure out another<br>technology just to tease the sql out of it<br></blockquote><br>I'm not sure how we could move away from liquibase. We would have to <br>provide a set of SQL scripts (cross-platform too) that would have to be <br>run on your database to upgrade keycloak. Then there is the Java-based <br>migrators that run after this to message the data with any new <br>transformations.<br><br><br><br>-- <br>Bill Burke<br>JBoss, a division of Red Hat<br><a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br></div></div>_______________________________________________<br>keycloak-dev mailing list<br><a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></div></blockquote></div><br></div></blockquote></div><br></div>