Re: An observation about default column value
- From: "Jonathan Lewis" <jonathan@xxxxxxxxxxxxxxxxxx>
- To: <gints.plivna@xxxxxxxxx>, "oracle list" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 3 Feb 2006 15:54:42 -0000
Any comments ?
Setting the default to an explicit null is the
advice from the manuals, so I supposed there's
no better option.
I guess the slight change in the data dictionary
means the implied default value of col$.default$
is 'null' (as opposed to NULL).
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/appearances.html
Public Appearances - schedule updated 10th Jan 2006
----- Original Message -----
From: "Gints Plivna" <gints.plivna@xxxxxxxxx>
To: "oracle list" <oracle-l@xxxxxxxxxxxxx>
Sent: Friday, February 03, 2006 2:42 PM
Subject: An observation about default column value
We had an app where some columns had default values. So life changes
and now we don't need them. Question is how to get rid of them?
Of course one can alter table with default value null. It seems that
functionally result is the same as without ever declared default value
for the column although data dictionary return different results...
Any comments? ;)
--
http://www.freelists.org/webpage/oracle-l
- References:
- An observation about default column value
- From: Gints Plivna
Other related posts:
- » An observation about default column value
- » Re: An observation about default column value
Regards
We had an app where some columns had default values. So life changes and now we don't need them. Question is how to get rid of them?
- An observation about default column value
- From: Gints Plivna