Message-ID: <362EE91B.879374AA@sferacarta.com>
Date: Thu, 22 Oct 1998 10:13:15 +0200
From: "Jose' Soares" <jose@sferacarta.com>
MIME-Version: 1.0
To: Byron Nikolaidis <byronn@insightdist.com>
CC: Sferacarta Software <sferac@bo.nettuno.it>,
	pgsql-interfaces@postgresql.org,
	"pgsql-hackers@hub.org" <pgsql-hackers@hub.org>
Subject: Re: [HACKERS] Re: [INTERFACES] Odbc parser error
References: <8440.980917@bo.nettuno.it> <3601721B.B2493AA3@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Byron Nikolaidis wrote:
> 
> Jose' Soares (Sferacarta Software) wrote:
> 
> > Hi all,
> >
> > Seems that ODBC driver have some problems while it translate Access
> > commands.
> > I created a form with a subform joined by two columns.
> >
> > after the Access Addnew event, log file returns the following error:
> > -----------------------------------------------------------------------
> > conn=75511800, query='SELECT "risanamento"."oid" FROM "risanamento" WHERE (("distretto" =  '' ) AND ("progressivo" =  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'
> > ------------------------------------------------------------------------
> > NB: Note that parser translate ("progressivo" =  NULL) instead of
> > ("progressivo" IS NULL).
> >
> >
> 
> Yes, the NULL works for parameters of an update statement, where Access would specify a statement such as "update table set param =
> ? where x = 1".  But it doesn't work in a select statement.  I don't think I have much to work with here.  The statement comes in as
> something like "select * from table where x = ?".  I have to replace the ? with something.  On updates, 'NULL' works fine.
> 
> I'm not sure what to do about this.  On other dbms, parameter passing is handled through a separate protocol to the backend, usually
> after a prepare statement, so on these its no problem to send a null, or large amounts of ascii/binary data, without having to worry
> about direct substitution into the sql string or hitting the upper limit of the statement string.  I think until Postgres has such
> as protocol for parameter substitution/passing, it will be difficult to fix this problem.
> 
> Any suggestions?
> 
Yes, I would to suggest a way to solve this problem because in Access we
can't link two tables
by a numeric field, for example:

I have 2 tables:

ORDER_MASTER:		ORDER_DETAIL:
--------------		--------------
numero	SERIAL	<--->	numero	SERIAL
...			...

When I try to create a new ORDER, the connection goes down with message:

# conn=75511800, query='SELECT "order_detail"."numero" FROM
"order_detail" WHERE ("numero" =  NULL )'
# ERROR from backend during send_query: 'ERROR:  parser: parse error at
or near "null"'


I know this is not standard but Access understand both syntaxes (i.e.:

SELECT * FROM table WHERE field IS NULL;      =  SELECT * FROM table
WHERE field = NULL;
SELECT * FROM table WHERE field IS NOT NULL;  =  SELECT * FROM table
WHERE field <> NULL;

Why not to get PostgreSQL to understand it also ?

Thank you for any help
        Jose'