0035653: update.database can fail updating src tables with a check constraint where more than one column participates

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #35653		[ All Revisions ] [ Back to Issue ]
Summary	0035653: update.database can fail updating src tables with a check constraint where more than one column participates

Revision	2017-09-12 12:55 by alostale
Description	Having DB check constraint for a datasource table that is computed based on more than one column, update.database can fail when adding changes to that table. This can occur if for a record more than one column participating in that contraint gets modified and even the whole changes fulfills the constraint, individual ones don't. In the case described in steps to reproduce section, checking executed DB statements we can see: UPDATE OBCQL_QUERY_COLUMN SET UPDATED = $1, UPDATEDBY = $2, HAS_LINK = $3 WHERE OBCQL_QUERY_COLUMN_ID = $4 parameters: $1 = '2017-09-12 12:38:30.269373', $2 = '0', $3 = 'Y', $4 = '28F920CD36E14AFBB2025802363E8B02' UPDATE OBCQL_QUERY_COLUMN SET UPDATED = $1, UPDATEDBY = $2, AD_TAB_ID = $3 WHERE OBCQL_QUERY_COLUMN_ID = $4 parameters: $1 = '2017-09-12 12:38:30.280567', $2 = '0', $3 = '186', $4 = '28F920CD36E14AFBB2025802363E8B02' UPDATE OBCQL_QUERY_COLUMN SET UPDATED = $1, UPDATEDBY = $2, CAN_BE_FILTERED = $3 WHERE OBCQL_QUERY_COLUMN_ID = $4 parameters: $1 = '2017-09-12 12:38:30.291775', $2 = '0', $3 = 'Y', $4 = '28F920CD36E14AFBB2025802363E8B02' Note that changes in individual columns are applied independently, so it's possible to leave row in a temporary inconsistent state.

Revision	2017-09-12 12:43 by alostale
Description	After updating a module version containing widgets compilation crashed (see attached log).