Changes between Initial Version and Version 1 of Ticket #35787, comment 3


Ignore:
Timestamp:
Jan 18, 2025, 3:36:11 PM (4 weeks ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35787, comment 3

    initial v1  
    11Thanks for investigating Chris!
    22
    3 I think this simply cannot be fixed on Oracle as once a column had a `DEFAULT` assigned to it, which is a pre-requisite for adding a field to a table with existing rows for example, Oracle doesn't allow you to drop it [https://docs.oracle.com/cd//B19306_01/server.102/b14200/statements_3001.htm#sthref5162 per their docs]
     3I think this simply cannot be fixed on Oracle as once a column had a `DEFAULT` assigned to it, which is a pre-requisite for adding a field to a table with existing rows for example, it doesn't allow you to drop it [https://docs.oracle.com/cd//B19306_01/server.102/b14200/statements_3001.htm#sthref5162 per their docs]
    44
    55> If a column has a default value, then you can use the `DEFAULT` clause to change the default to `NULL`, but you **cannot remove the default value completely**. That is, if a column has ever had a default value assigned to it, then the `DATA_DEFAULT` column of the `USER_TAB_COLUMNS` data dictionary view will always display either a default value or `NULL`.
Back to Top