From: wieck@debis.com
To: jose@sferacarta.com
Cc: bruce@cenderis.demon.co.uk
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] NULL
Date: Tue, 16 Nov 1999 15:16:08 +0100 (MET)
Message-ID: <m11njOy-0003kLC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <38315E00.4CDB885F@sferacarta.com>
> > > 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@debis.com (Jan Wieck) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: wieck@debis.com, jose@sferacarta.com, bruce@cenderis.demon.co.uk
Subject: Re: [SQL] NULL
In-Reply-To: <m11njOy-0003kLC@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox