Fadoua
There's a bug in the current InstantDB where, if you specify a column list
in an INSERT it causes NULLs to be overridden with the default value. If you
omit the column list and specify all values this does not happen. The
following few lines of sample script illustrate the difference:
e drop table tmp;
e create table tmp (int1 int default 1, char1 char(10));
e insert into tmp (int1,char1) values (null,"line2");
e insert into tmp values (null,"line2");
q select * from tmp;
Is this the bug you are having problems with? If so, use the work around of
omitting the column list. The bug will be fixed in a future release.
Regards
Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: Fadoua Ouerdiane <ouerdiane@internolix.com>
To: instantDB@enhydra.org <instantDB@enhydra.org>
Date: 10 May 2000 19:07
Subject: InstantDB: Default value
Dear Peter
I have created a table, which has a column with a default value. After
insertion of a row containing the Null value in this column, I noted, that
the value by default was not seized.
Can you tell me please, what I have to do.
I appreciate your help and thank you in advance .
with best regards
============================
Dipl.-Inf. Fadoua Ouerdiane
manager
Internolix Tunisia
Immeuble l'arche du lac 2eme etage
2045 les berges du lac deTunis
Tel: +216 [0] 1 960 599
Fax: +216 [0] 1 960 576
email: internolix.gnet.tn
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|