Skip site navigation (1) Skip section navigation (2)

Re: Parse Errors with prepared query

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Ed Brown <ebrown(at)arcompanies(dot)net>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Parse Errors with prepared query
Date: 2002-05-09 01:17:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
> Ed Brown wrote:
> Thanks for any guidance on the following issue:
> I am running PostgreSQL 7.2.1 on redhat, accessing from Windows 2000
> Professional. I installed ODBC off the web
> site. I have a data upload application written in Delphi which moves
> data from an Access table. I've used it at least ten times with an
> Interbase database, and have run something on the order of half a
> million records through it without apparent errors. It composes a
> statement of the form.
>     Insert into <Table> Fields<Field1,Field2,Field3,...> Values
>  (?,?,?,...);
> It prepares the statement and then executes it for each record in the
> Access table. On one table with about 33,000 record and twenty-some
> fields it works fine. On another table with 11 fields and about 6,000
> records it fails. It fails to execute the query, and returns an error,
> usually of the form
>     ERROR:  parser: parse error at or near "("

Could you check the server side log(debug mode if possible)
and see what query issued exactly at the error ?

> Also: does anyone know, am I saving any time by using a prepared
> statement?  It appears that the driver is just holding the statement
> and inserting the parameters, then passing to the server. Is that
>  correct?

Yes. Unfortuantely there's no prepare functionality in
PostgreSQL yet and so the psqlodbc driver has little to
do with SQLPrepare.

Hiroshi Inoue

In response to

pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2002-05-09 01:36:42
Subject: Re: mylog() + qlog() implementation
Previous:From: Tom LaneDate: 2002-05-08 04:40:04
Subject: Re: mylog() + qlog() implementation

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group