The validationaccount_item table's not-null constraints break add participants functionality in Oracle
Description
Attachments
is depended on by
is duplicated by
relates to
Activity
Roland Groen September 1, 2013 at 3:57 PM
For oracle, the patch on the validator will not work, '' is null on Oracle. The DDL update script:
ALTER TABLE VALIDATIONACCOUNT_ITEM
MODIFY (FIRST_NAME NULL);
ALTER TABLE VALIDATIONACCOUNT_ITEM
MODIFY (SURNAME NULL);
Aaron Zeckoski July 11, 2013 at 4:09 PM
That may be true, if so we will need an oracle migration script which removes the constraint. Removing it from MySQL as well could cause issues though so it will be something that Oracle users have to maintain separately.
Brian Baillargeon July 11, 2013 at 12:01 PM
If I remember correctly I tried this approach and Oracle treated empty strings as NULL
Hudson CI Server July 11, 2013 at 11:41 AM
Integrated in reset-pass trunk #482 (See http://builds.sakaiproject.org:8080/job/reset-pass%20trunk/482/)
attempting to fix this without altering the schema, made empty string the object default for ValidationItem (Revision 126916)
Result = SUCCESS
Aaron Zeckoski July 11, 2013 at 11:31 AM
Needs to be tested for Oracle
"I'm getting constraint violations, the FIRST_NAME column cannot be null (though a user account created through the "add participants" screen cannot yet have a first or last name...)
I'm getting the same behaviour on http://qa5-us.sakaiproject.org/
If I disable the two constraints, everything seems to work fine."
Curtis Van-Osch
I too have had constraint issues when deploying to our development server which is running Oracle.