From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | applixware-list(at)applix(dot)com |
Cc: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
Subject: | Re: AWL: Re: tm1 |
Date: | 1999-11-12 06:54:20 |
Message-ID: | 382BB99C.7B8B94E0@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> People may have problems with the NULL statements with some versions
> of PostgreSQL. I have information about editing the applix macro
> on that creates the tables my web site:
> http://www.radix.net/~cobrien/applix/applix.txt
Just in case someone cares ;)
The "NULL" constraint for a column definition is not defined in SQL92,
and is not necessary and could be dropped from Applix's definition of
the table. The default behavior of any column defined in SQL is to
allow NULL values.
Postgres does not implement this redundant syntax extension because
yacc-style parsers such as the one used in Postgres find the use of
the bare NULL an ambiguous context. Presumably that is why SQL92 does
not define it.
However, I see that in a limited context, such as a bare NULL with no
other qualifiers, yacc can handle its use. I'll add it to Postgres'
next release...
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 1999-11-12 07:39:55 | Re: AW: [HACKERS] Re: [GENERAL] users in Postgresql |
Previous Message | Tom Lane | 1999-11-12 06:14:43 | Re: [HACKERS] compression in LO and other fields |