Re: Forms 6.0 and interaction with table/column with default value

From: ml <mluo_at_yesic.com>
Date: Tue, 12 Dec 2000 19:50:29 -0500
Message-ID: <MKzZ5.84$EeC4.16187614_at_news.randori.com>


[Quoted] maybe you have a base table field related to the data column , Oracle Form [Quoted] just reconstrunct the insert statement and inside the statement there is a data column wihch is absent in you statement running in SQL*Plus.

That causes the difference.

"Matt B." <mcb_at_ds.znet.com> wrote in message news:t3b7ntlp2nhr46_at_corp.supernews.com...
> I have a table in the database that has a default value on a particular
 column:
>
> Example (not my actual table but I'm keeping the example simple):
>
> CREATE TABLE MY_TABLE
> (MY_DATA VARCHAR2(50) NOT NULL,
> INSERT_DT_TIME DATE DEFAULT SYSDATE NOT NULL);
>
> If I insert something into the table outside of Forms (like in SQL*Plus),
 this
> works fine:
>
> INSERT INTO MY_TABLE(MY_DATA)
> VALUES('STUFF');
>
> It populates INSERT_DT_TIME for me with no problem even though I didn't
 specify
> it.
>
> However, I now have a form where MY_TABLE is the base table for a block.
 I
> give the user the items MY_DATA and INSERT_DT_TIME, but I leave
 INSERT_DT_TIME
> as optional in the form since I'm expecting the default at the table level
 to
> populate it if the user doesn't.
>
> When I commit a record in the form with a null INSERT_DT_TIME, I get an
> ORA-1400 error on the INSERT_DT_TIME column. Why is this? Shouldn't the
> table's default value of SYSDATE populate that column for me when I don't
 do it
> ahead of time?
>
> Thanks,
>
> Matt
>
>
Received on Wed Dec 13 2000 - 01:50:29 CET

Original text of this message