Project:
| View Revisions: Issue #29284 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0029284: Oracle: onCretateDefault not executed for appended non mandatory columns | ||
| Revision | 2015-03-23 09:21 by AugustoMauch | ||
| Description | When a new non mandatory column with an onCreateDefault different to its default is appended, the new column has null values instead of the one defined in the onCretateDefault. OnCreateDefault should prevail over the default. This can be reproduced in Oracle, in PostgreSQL it works as expected. |
||
| Revision | 2015-03-17 08:05 by alostale | ||
| Description | When a new non mandatory column with an onCreateDefault different to its default is appended, the new column has null values instead of the one defined in the onCretateDefault. OnCreateDefault should prevail over onCreateDefault. This can be reproduced in Oracle, in PostgreSQL it works as expected. |
||
| Revision | 2015-03-16 10:09 by alostale | ||
| Description | When a new non mandatory column with an onCreateDefault (different to its default, if any) is appended, the new column has null values instead of the one defined in the onCretateDefault. This can be reproduced in Oracle, in PostgreSQL it works as expected. In case the new non mandatory column has a default value different to its onCreateDefault, default value is applied but onCreateDefault should prevail over onCreateDefault. |
||
| Revision | 2015-03-16 09:53 by alostale | ||
| Description | When a new non mandatory column with an onCreateDefault (different to its default, if any) is appended, the new column has null values instead of the one defined in the onCretateDefault. This can be reproduced in Oracle, in PostgreSQL it works as expected. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |