The Hermit Hacker <scrappy@hub.org> writes:
> Moved to pgsql-hackers@postgresql.org (where the developers hang out)
> > The NULL contraint: PostgreSQL only allows NOT NULL (NULL being the
> > default). I altered the backend grammar for this one.
>
> Patch?
OK. The patch to gram.y is almost certainly wrong: it's just a hack
to get NULL acceptable---it should surely go in the same place as the
check for NOT NULL.
The floating point literal change is probably right, but it may break
things (it may well cause more things to be regarded as floats than
should be). Again, somebody who knows about this stuff definitely
needs to check.
I hope this helps all the same.
*** /mnt/1gig2/postgres/make/pgsql/src/backend/parser/gram.y Fri Apr 17 05:12:56 1998
--- gram.y Mon Apr 20 22:59:01 1998
***************
*** 735,740 ****
--- 735,741 ----
;
ColQualifier: ColQualList { $$ = $1; }
+ | NULL_P { $$ = NULL; }
| /*EMPTY*/ { $$ = NULL; }
;
*** /mnt/1gig2/postgres/make/pgsql/src/backend/parser/scan.l Wed Apr 8 07:35:00 1998
--- scan.l Mon Apr 20 23:22:16 1998
***************
*** 153,159 ****
xmstop -
integer -?{digit}+
! real -?{digit}+\.{digit}+([Ee][-+]?{digit}+)?
param \${integer}
--- 153,159 ----
xmstop -
integer -?{digit}+
! real -?{digit}*\.{digit}+([Ee][-+]?{digit}+)?
param \${integer}