Harish Kumar Vor 6 Jahren Hi David,I tried it and upgrade process did update the database schema as expected. Writing upgrade process seems good considering modular approach and production environment. But it seems at least to me an overhead considering continuous changes to schema during development phase.Is there a way to update the database schema as per service.xml during development phase to reduce this upgrade process overhead?Regards,Harish Melden Sie sich an, um auf diesen Beitrag zu antworten. Antworten als... Abbrechen David H Nebinger Harish Kumar Vor 6 Jahren The upgrade process and the Liferay-Require-SchemaVersion thing is definitely not meant for development, it's meant for releases.Personally I tend to stick to HSQL for as much of the service development that I can, it is just so easy to copy the DB script and restore later on, effectively dropping the changes made during previous service deployment. Melden Sie sich an, um auf diesen Beitrag zu antworten. Antworten als... Abbrechen
David H Nebinger Harish Kumar Vor 6 Jahren The upgrade process and the Liferay-Require-SchemaVersion thing is definitely not meant for development, it's meant for releases.Personally I tend to stick to HSQL for as much of the service development that I can, it is just so easy to copy the DB script and restore later on, effectively dropping the changes made during previous service deployment. Melden Sie sich an, um auf diesen Beitrag zu antworten. Antworten als... Abbrechen
Adam Steiner Vor 3 Jahren - Bearbeitet This blog post needs to be included in the Official documentation! A straight-forward explanation of how the Bundle Version, Liferay-Require-SchemaVersion, and ServiceBuilder build.number relate (or don't) to each other wouldn't hurt either. Melden Sie sich an, um auf diesen Beitrag zu antworten. Antworten als... Abbrechen