Re: Default Value
- From: Alberto <alberto.ceriotti@xxxxxxxxx>
- Date: Mon, 31 Mar 2008 05:39:42 -0700 (PDT)
On 30 Mar, 12:19, Frank van Bortel <frank.van.bor...@xxxxxxxxx> wrote:
web.Hunter wrote:
Hi, I've a problem with default value of integer data type: my
software work fine with oracle version 8, but fail with 11g version.
The problem is on sql insert command because are often omitted some
columns for use the default value. If the column omitted has a integer
data type, on oracle 8 the command is succesful executed; viceversa
the command faild on 11g oracle version: the response message return
an unexpected null value on a not-null column. I repeat: Only on
integer data type column.
I suppose that there is a configuration value that is possible to
modified but I don't know what and here.
If table definitions are equal (especially the
number column - integers are numbers); then this should
work:
insert into a values (col_1, col_2,,col4);
col_3 being you number column:
...
col_3 NUMBER NOT NULL default 42,
col_4 ...
If not, 11G evaluates in a different manner (table definition
against statement) than 8 did (given values, including defaults
on table).
If not, you may have found a a bug. Make sure you test this
against the latest patch version available
--
Regards,
Frank van Bortel
Top-posting in UseNet newsgroups is one way to shut me up
Hi, Frank
I've send more details to Helma
.
- References:
- Default Value
- From: web.Hunter
- Re: Default Value
- From: Frank van Bortel
- Default Value
- Prev by Date: Re: Default Value
- Next by Date: Re: Do all the legs of an "OR" with null comparisons get executed?
- Previous by thread: Re: Default Value
- Next by thread: Re: Default Value
- Index(es):
Relevant Pages
|
