Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #29284 All Revisions ] Back to Issue ]
Summary 0029284: Oracle: onCretateDefault not executed for appended non mandatory columns
Revision 2015-03-17 08:05 by alostale
Steps To Reproduce -For any non AD table add in xml files a non mandatory column with onCreateDefault 'A' and default 'B' (ensure this is the only change for that column in this table)
-Ensure this table has in DB at least one row
-Execute update.database
-Check new column values
   -> It is 'A' (default value) but it should be what onCreateDefault defines ('B')
Revision 2015-03-16 10:09 by alostale
Steps To Reproduce -For any non AD table add in xml files a non mandatory column with onCreateDefault 'A' (ensure this is the only change for that column in this table)
-Ensure this table has in DB at least one row
-Execute update.database
-Check new column values
   -> It is null but it should be what onCreateDefault defines ('B')

Another case:
-For any non AD table add in xml files a non mandatory column with onCreateDefault 'A' and default 'B' (ensure this is the only change for that column in this table)
-Ensure this table has in DB at least one row
-Execute update.database
-Check new column values
   -> It is 'A' (default value) but it should be what onCreateDefault defines ('B')
Revision 2015-03-16 09:53 by alostale
Steps To Reproduce -For any non AD table add in xml files a non mandatory column with onCreateDefault (ensure this is the only change for that column in this table)
-Ensure this table has in DB at least one row
-Execute update.database
-Check new column values
   -> It is null but it should be what onCreateDefault defines


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker