From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | jose(at)sferacarta(dot)com (jose soares) |
Cc: | bruce(at)cenderis(dot)demon(dot)co(dot)uk, pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] NULL |
Date: | 1999-11-16 14:16:08 |
Message-ID: | m11njOy-0003kLC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> > > It suppose to mean that NULLs are explicitly allowed in
> > > this field.
> > > Is this required by SQL-92?
> >
> > No, it's not required. This came up before with the examples from
> > "The Practical SQL Handbook". It would be nice to allow it, but there
> > was some reason why to do so would be non-trivial, which I forget.
> > Anyway, it's not in SQL-92.
> >
> Sorry, I don't understand why we need this feature. This is completely ou=
> t
> of standard.
>
> What's that mean ?
>
> - Is it a constraint to allow only NULL values ? (unuseful)
Useless? I NEED IT - URGENT - NOW - YESTERDAY.
Then I could create my tables with all required fields for
the future, but prevent that someone stores data in them
until I drop the constraint.
I vote for this :-)
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | maxsbox | 1999-11-16 18:17:07 | ODBC/Openlink/Delphi |
Previous Message | jose soares | 1999-11-16 13:37:05 | Re: [SQL] NULL |