From: | Hiroshi Saito <hiroshi(at)winpg(dot)jp> |
---|---|
To: | awessel(at)masterap(dot)nl |
Cc: | pgsql-odbc(at)postgresql(dot)org, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
Subject: | Re: Fwd: ODBC breaks on some machines |
Date: | 2011-09-30 12:28:25 |
Message-ID: | 4E85B5E9.6050903@winpg.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi.
Sorry very late reaction.
The method of CURSOR which you use may influence a result.
Would you be shown the reproducible code, if possible?
and, Please send mylog to Inoue-san with me.
I appreciate your perseverance. thanks.
Regards,
Hiroshi Saito
(2011/09/12 18:54), Albert wrote:
>
>
> Hi,
>
> We have a strange problem going on. The postgres ODBC breaks down at
> random at some machines.
>
> What happens is: Via ODBC we call an postgresql function (as example
> this: ) :
>
> select getmynumber('abc') as result;
>
> This works fine we can use the result in our application. However, on
> some of our customers PC's this suddenly stops working. We get an ODBC
> error Error -1:'' The only thing I can find in the odbc logging that is
> different opposed to the correct situation: QLExtendedFetch with return
> code -1 (SQL_ERROR)
>
> It seems random that this occurs. I cannot relate it to a windows patch,
> nor another software installation nor our own software. The problem,
> over the course of 2 years, happens every now and then on some random
> pc. The only thing we have found to get it working again is to reinstall
> Windows. (it has happened now on several XP and several Windows 7 machines)
>
> The client application uses MFC ODBC.
>
> I have logging of odbc, mylog and psqlodc available.
>
> Can somebody help with this?
> Kind regards,
> Albert Wessel
> *
> *
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2011-09-30 12:37:01 | Re: psqlodbc-09.00.0310 Crash issues with aggregate function based queries.. specifically SUM and AVG. |
Previous Message | noreply | 2011-09-29 22:20:19 | [ psqlodbc-Bugs-1011099 ] SQLStatistics returns A instead of D for descending index column |