Harish Kumar 6年 前 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 投票するためにはログインが必要です。 次として送信する: キャンセル David H Nebinger Harish Kumar 6年 前 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. 投票するためにはログインが必要です。 次として送信する: キャンセル
David H Nebinger Harish Kumar 6年 前 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. 投票するためにはログインが必要です。 次として送信する: キャンセル
Adam Steiner 3年 前 - 編集済み 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. 投票するためにはログインが必要です。 次として送信する: キャンセル