topic dbCreate strategy in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/dbcreate-strategy/m-p/23152#M11166 <HTML><HEAD></HEAD><BODY><SPAN>Current DbSchema strategies are:</SPAN><BR /><BR /><SPAN>&nbsp; CREATE, CREATE_DROP, DROP_CREATE, CHECK_VERSION</SPAN><BR /><BR /><SPAN>I would like one that CREATEs the schema if it doesn't already exist, but if it does already exist, then it runs CHECK_VERSION (and leaves the data alone).</SPAN><BR /><BR /><SPAN>i.e. I want schema creation to be an automatic part of my application bootstrap, not an explicit step that an admin must perform. (grails works this way quite well).</SPAN><BR /><BR /><SPAN>Is there a reason why this would be a bad idea? Could I contribute a patch to provide this behaviour?</SPAN></BODY></HTML> Mon, 20 Sep 2010 00:02:53 GMT mlawler 2010-09-20T00:02:53Z dbCreate strategy https://connect.hyland.com/t5/alfresco-archive/dbcreate-strategy/m-p/23152#M11166 Current DbSchema strategies are:&nbsp; CREATE, CREATE_DROP, DROP_CREATE, CHECK_VERSIONI would like one that CREATEs the schema if it doesn't already exist, but if it does already exist, then it runs CHECK_VERSION (and leaves the data alone).i.e. I want schema creation to be an automatic part of my applic Mon, 20 Sep 2010 00:02:53 GMT https://connect.hyland.com/t5/alfresco-archive/dbcreate-strategy/m-p/23152#M11166 mlawler 2010-09-20T00:02:53Z Re: dbCreate strategy https://connect.hyland.com/t5/alfresco-archive/dbcreate-strategy/m-p/23153#M11167 <HTML><HEAD></HEAD><BODY><SPAN>adding support for that capability in the implementation is wanted.&nbsp;&nbsp; but i don't want to expose that functionality as supported or normal usage.</SPAN><BR /><BR /><SPAN>i recently switched from using an enum to a string configuration for that.&nbsp; this way, the API can expose constant strings for CREATE_DROP (for testing) and CHECK_VERSION (in production) as those are the only ones that I want to see exposed to all users.</SPAN><BR /><BR /><SPAN>all the other strategies (including the one you propose) should only be used if you know what you're doing.&nbsp; i'm ok with supporting these, but not to have constants for those in the API.</SPAN><BR /><BR /><SPAN>if you want to contribute, sign the contributor agreement (see wiki), create a jira issue and associate a patch with the issue.</SPAN></BODY></HTML> Mon, 20 Sep 2010 13:04:17 GMT https://connect.hyland.com/t5/alfresco-archive/dbcreate-strategy/m-p/23153#M11167 tombaeyens 2010-09-20T13:04:17Z