Re: [BUGS] BUG #11608: ODBC driver crashes after wrong password entered

From: "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp>
To: Eric Hill <Eric(dot)Hill(at)jmp(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #11608: ODBC driver crashes after wrong password entered
Date: 2014-10-14 06:46:08
Message-ID: 543CC6B0.2010001@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-odbc

(2014/10/12 2:28), Eric Hill wrote:
> Hey, Hiroshi,
>
> I am developer on the JMP statistical visualization tool dev team
> (www.jmp.com <http://www.jmp.com>). This is a desktop application that
> runs on Windows and Mac. Our product uses ODBC calls to connect to ODBC
> data sources and retrieve data. We have both 32-bit and 64-bit versions
> of the product. The scenario we are seeing this problem with is 64-bit
> JMP talking a Windows PostgreSQL server. The connection string is
> coming from the driver. I looked in the driver dialog to see if there
> was a way to specify SSL or something, but I did not see anything.

Unfortunately I can't reproduce the crash here.
What's your calling sequence of ODBC APIs after SQLDriverConnect()
with bad password?

regards,
Hiroshi Inoue

--
I am using the free version of SPAMfighter.
SPAMfighter has removed 12751 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

Do you have a slow PC? Try a Free scan
http://www.spamfighter.com/SLOW-PCfighter?cid=sigen

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message t.chaumeny 2014-10-14 09:12:21 BUG #11671: UNACCENT call with constant arg evaluated for each row
Previous Message David G Johnston 2014-10-14 05:48:28 Re: Question

Browse pgsql-odbc by date

  From Date Subject
Next Message Jade Koskela 2014-10-15 05:38:55 Re: crash bug on closed connection
Previous Message Jade Koskela 2014-10-14 05:27:21 Re: crash bug on closed connection