I would like for you to also consider adding the following to gram.y for
version 6.5:
| NULL_P '=' a_expr { $$ = makeA_Expr(ISNULL, NULL, $3,
NULL); }
I know there was some discussion about this earlier including comments
against this. Access 97 is now generating the following statement and
error:
SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5
432;UID=kari;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROW
VERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS='
conn=154616224,
query='SELECT "RentalOrders"."rentalorderlinesid" FROM "rentalorderlines"
"RentalOrders" WHERE ( NULL = "rentalorderid" ) '
ERROR from backend during send_query: 'ERROR: parser: parse error at or
near "="'
The above code changed allows Access 97 to work correctly. I would be happy
to consider any other possible alternatives.
Thanks, Michael
-----Original Message-----From: Bruce Momjian [SMTP:maillist@candle.pha.pa.us]Sent: Saturday, March 13, 1999
10:14PMTo: Michael DavisCc: hackers@postgreSQL.orgSubject: Re: [HACKERS] parser enhancement request for 6.5
Applied.
[Charset iso-8859-1 unsupported, filtering to ASCII...]> I have a problem with Access97 not working properly when
entering
new> records using a sub form, i.e. entering a new order/orderlines or
master and> detail tables. The problem is caused by a SQL statement that
Access97 makes> involving NULL. The syntax that fails is "column_name" = NULL.
The> following attachment was provided by -Jose'-. It contains a very
small> enhancement to gram.y that will allow Access97 to work properly
with sub> forms. Can this enhancement be added to release 6.5?> > <<gram.patch>> > Thanks, Michael>
[Attachment, skipping...]
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel
Hill,Pennsylvania
19026