(You) 7 Years Ago [...] Julian Pfeil: Why doesn't deploying the new module version update/re-create the table? Support for this has been removed. It was always buggy anyway for SB to determine what really needed to change... [...] Read More Please sign in to reply. Reply as... Cancel
(You) 6 Years Ago [...] That functionality was deprecated in Liferay 7 since it didn't work very well. Instead you are encouraged to build out actual upgrade logic:... [...] Read More Please sign in to reply. Reply as... Cancel
Szymon Lipiec 2 Years Ago - Edited So we need to have two jar files? One to activate/register the module (from 0.0.0 to 1.0.0), and second to do the upgrade steps? What if I have a new module, which doesn't exist, and I want to upgrade him later using upgrade:execute? To register the upgrade step I need to have a module already registered, otherwise, the upgrade step won't be recognized. Please sign in to reply. Reply as... Cancel David H Nebinger Szymon Lipiec 2 Years Ago - Edited Not sure I understand your question... The upgrade process should be tied to the module that you want to upgrade, because we're inherently changing the version number of the module. So when you define the 1.0.0 -> 1.0.1 version, the end result is that the module will be 1.0.1. I have been known to create a separate module w/ an upgrade process defined that invoked other services (i.e. to create users, roles, pages, etc) and in that case the module still is tracking its own version, but this won't really apply to your SB module since you're trying to manage DB changes along with your new entity changes... Please sign in to reply. Reply as... Cancel Szymon Lipiec David H Nebinger 2 Years Ago - Edited I don't have an SB module. I just created a simple UpgradeStepRegistrator class with few steps, but they are not working, because I don't have a record in the Release_ table. So my question is, how to register a module in the Release_ table, before adding an upgrade process. Please sign in to reply. Reply as... Cancel David H Nebinger Szymon Lipiec 2 Years Ago - Edited Do you have a registration for "0.0.0" -> whatever version you're at? The upgrade process system assumes that no record is equivalent to "0.0.0" so you need that initial step (even if it is a dummy step) to get your Release_ entry created and started. If, for example, you only defined a "1.0.0" -> "1.0.1" upgrade process, it effectively would never run because the current version (since there is no Release_ entry yet) is "0.0.0" and there's no way to go from there to any of the other versions. Please sign in to reply. Reply as... Cancel
David H Nebinger Szymon Lipiec 2 Years Ago - Edited Not sure I understand your question... The upgrade process should be tied to the module that you want to upgrade, because we're inherently changing the version number of the module. So when you define the 1.0.0 -> 1.0.1 version, the end result is that the module will be 1.0.1. I have been known to create a separate module w/ an upgrade process defined that invoked other services (i.e. to create users, roles, pages, etc) and in that case the module still is tracking its own version, but this won't really apply to your SB module since you're trying to manage DB changes along with your new entity changes... Please sign in to reply. Reply as... Cancel Szymon Lipiec David H Nebinger 2 Years Ago - Edited I don't have an SB module. I just created a simple UpgradeStepRegistrator class with few steps, but they are not working, because I don't have a record in the Release_ table. So my question is, how to register a module in the Release_ table, before adding an upgrade process. Please sign in to reply. Reply as... Cancel David H Nebinger Szymon Lipiec 2 Years Ago - Edited Do you have a registration for "0.0.0" -> whatever version you're at? The upgrade process system assumes that no record is equivalent to "0.0.0" so you need that initial step (even if it is a dummy step) to get your Release_ entry created and started. If, for example, you only defined a "1.0.0" -> "1.0.1" upgrade process, it effectively would never run because the current version (since there is no Release_ entry yet) is "0.0.0" and there's no way to go from there to any of the other versions. Please sign in to reply. Reply as... Cancel
Szymon Lipiec David H Nebinger 2 Years Ago - Edited I don't have an SB module. I just created a simple UpgradeStepRegistrator class with few steps, but they are not working, because I don't have a record in the Release_ table. So my question is, how to register a module in the Release_ table, before adding an upgrade process. Please sign in to reply. Reply as... Cancel David H Nebinger Szymon Lipiec 2 Years Ago - Edited Do you have a registration for "0.0.0" -> whatever version you're at? The upgrade process system assumes that no record is equivalent to "0.0.0" so you need that initial step (even if it is a dummy step) to get your Release_ entry created and started. If, for example, you only defined a "1.0.0" -> "1.0.1" upgrade process, it effectively would never run because the current version (since there is no Release_ entry yet) is "0.0.0" and there's no way to go from there to any of the other versions. Please sign in to reply. Reply as... Cancel
David H Nebinger Szymon Lipiec 2 Years Ago - Edited Do you have a registration for "0.0.0" -> whatever version you're at? The upgrade process system assumes that no record is equivalent to "0.0.0" so you need that initial step (even if it is a dummy step) to get your Release_ entry created and started. If, for example, you only defined a "1.0.0" -> "1.0.1" upgrade process, it effectively would never run because the current version (since there is no Release_ entry yet) is "0.0.0" and there's no way to go from there to any of the other versions. Please sign in to reply. Reply as... Cancel