Message-ID: <36DD1FD2.11561615@mediacom.it>
Date: Wed, 03 Mar 1999 08:41:07 -0100
From: Valerio Santinelli <tanis@mediacom.it>
MIME-Version: 1.0
To: Byron Nikolaidis <byronn@insightdist.com>
CC: "'pgsql-interfaces@postgreSQL.org'" <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Foreign Keys
References: <93C04F1F5173D211A27900105AA8FCFC145219@lambic.prevuenet.com>
	<36DC61D6.6DF4E87D@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Byron Nikolaidis wrote:

> Michael Davis wrote:
>
> > Here is the psqlodbc.log file.  The first time the form opens, it correctly
> > opens the first rentalorder.  I immediately moved to the new record in
> > Access which opens a message box with an ODBC error (no description).  I the
> > blank rental order looks okay but the rental order lines records all have
> > errors.  Even if I move back to a valid record, the order lines will show
> > only errors.
> >
> The second problem is this:
>
> conn=153237224, query='SELECT "RentalOrders"."rentalorderlinesid" FROM "rentalorderlines"
> "RentalOrders" WHERE ("rentalorderid" =  NULL ) '
> ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
> STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
>
> Since postgres will not recognize the syntax (where 'col' = null)...  it only recognizes
> "isnull".  I was hoping someone would have added the ability for the parser to handle this at
> some point (Hey Dave, maybe you could contribute something here man :-).

The second problem is affecting my system as well.. do you think that there's a way around it without waiting for someone to patch the PostgreSQL code ?

--

C'ya!

Valerio Santinelli a.k.a. TANiS
[tanis@mediacom.it]+:+[http://www.mediacom.it/~tanis]