The following sections describe such improvements:
Typical database upgrade errors are due to changes in the model that are incompatible with the existing database, namely:
unique constraint violations when creating a primary key or a unique index over data with duplicate records
foreign key constraint violations when foreign keys over attributes with no corresponding entries in the foreign database table
foreign key constraint violations when deleting records of static entities that are in use by other database tables
database column length violations when reducing the length of a column that contains data longer than the new length
database column type violations when changing the datatype of a column that contains data that cannot be converted to the new datatype
generic timeouts creating indexes for a database table with a very large number of records
Starting with 220.127.116.11, any of the above errors abort the deployment of a solution before changing the application meta-model. Furthermore, in SQL Server all DDL statements executed before these errors are reverted as they occur in a single transactions. In MySQL and Oracle, DDL statements issue an implicit commit, thus DDL statements executed before the error are not reverted.
Also the message now contains a link to access detailed error log in case of database upgrade error, and messages were updated for clarity.
Incompatible dependencies may occur when deploying a solution via Service Center (Service Center does not validate dependencies prior to the deployment as LifeTime does). Starting with 18.104.22.168, deployments in production environments consider incompatible dependency messages as fatal errors and abort the deployment with no impact to the running applications. Non production environments have a different behavior and will continue the solution deployments. This behavior can be customized for both production and nonproduction environments. Please contact firstname.lastname@example.org for further details.
Starting with 22.214.171.124, solution deployments via Service Center are consistent with the LifeTime deployment behavior and only deploy the modules effectively included in the solution. In prior versions, the platform also deployed solution dependencies (the producers required by the solution). This means solution deployments no longer publish commonly used modules like “Users” and “Rich Widgets”. This also means solution deployments via Service Center are now as fast as deployments via LifeTime. If you need to deploy the dependencies, just include them in the solution.
Good news! All you have to do is upgrade to the OutSystems Platform 126.96.36.199. If you have any feedback, please let us know.