Re: odbc driver update issues - Mailing list pgsql-odbc

From Michael Shulman
Subject Re: odbc driver update issues
Date
Msg-id c3f821000602180659r1b2f6978h7ca616cd47dbc4c5@mail.gmail.com
Whole thread Raw
In response to odbc driver update issues  ("simon smith" <minos46@hotmail.com>)
List pgsql-odbc
This looks like the same error that I just found myself getting, which
was fixed on changing the driver options from ANSI to Unicode (to
agree with my database).  This discrepancy was apparently causing the
driver to fail to put quotation marks around parameters, thus causing
them to be interpreted as columns, which didn't exist.

HTH

On 2/11/06, simon smith <minos46@hotmail.com> wrote:
> I been looking at upgrading from psqlodbc-08_00_0102 to psqlodbc-08_01_0200
>
> Have there been changes in how stored procedures are called between these
> version? As I am having problems. All runs fine with psqlodbc-08_00_0102
> including my stored procedures. However when I move to the new
> psqlodbc-08_01_0200 driver the only sql that works in dynamic sql. The
> stored procedures return errors. eg
>
> SELECT MESSAGE, ID_NUMBER FROM SYSTEM_MESSAGES WHERE TITLE = ? ORDER BY
> MSGSEQ ('INVALIDUSER') being the place holder var
> Source:Microsoft OLE DB Provider for ODBC Drivers
> Description:Error while executing the query;
> ERROR:  column "xxx" does not exist
>
> the "xxx" is not a column, its a parameter.
>
> has the way that paramerters are handled changed?
>
> Please Help
>
> Regards
> Simon
>
> _________________________________________________________________
> Are you using the latest version of MSN Messenger? Download MSN Messenger
> 7.5 today! http://messenger.msn.co.uk
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

pgsql-odbc by date:

Previous
From: "simon smith"
Date:
Subject: odbc driver update issues
Next
From: Diwakoe
Date:
Subject: exporting table from mssql to postgre using odbc