From: | Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | AW: [HACKERS] DROPping tables with SERIALs |
Date: | 1998-12-03 20:20:38 |
Message-ID: | 219F68D65015D011A8E000006F8590C60180FAB1@sdexcsrv1.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> >> No, I think it should *only* substitute for NULL. Why assume
>> >> zero is special?
>>
>> > As I remember this is how SERIAL works in Informix.
>>
>> Ah. OK, if that's what they do then I agree we ought to act the
same.
>I hope that this wasn't to say that the SERIAL should substitute
for 0
>as well as NULL. That would be quite annoying. I say stick to
NULL.
Yes, 0 is an allowed value for a serial, that should not be
substituted.
I like the behavior that a NULL is substituted.
Informix is a little dull here. It forces a not null constraint, and
will therefore
raise an error if a null is inserted. I don't see any advantage in
this behavior.
(You are forced to skip the field in the insert statement to get a
generated serial)
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-12-04 00:19:50 | Re: [HACKERS] Two pg_dump ugly bugs :-( |
Previous Message | Jackson, DeJuan | 1998-12-03 19:49:40 | RE: [HACKERS] DROPping tables with SERIALs |