Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes witherror - Mailing list pgsql-odbc

From Inoue, Hiroshi
Subject Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes witherror
Date
Msg-id 676c0898-375d-ddad-3a70-4528b4165b82@dream.email.ne.jp
Whole thread Raw
In response to RE: SQLExecDirectW returns SQL_SUCCESS even if sql finishes witherror  ("Takahashi, Ryohei" <r.takahashi_2@jp.fujitsu.com>)
Responses Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-odbc
Hi Takahashi-san,

Could you please tell the customer that it's meaningless to set  
client_min_messages to 'fatal' or 'panic'?

regards,
Hiroshi Inoue

On 2018/11/01 15:57, Takahashi, Ryohei wrote:
> Hi Inoue-san,
>
>
> Thank you for replying.
>
>
>> Why do you set client_min_messages to fatal in the first place?
> Actually, my customer used PostgreSQL with default settings at first.
> He wanted to reduce server logs later and set log_min_messages = fatal and client_min_messages = fatal.
>
> I know client_min_messages does not reduce server logs and recommended him to change client_min_messages again.
>
>
> Anyway, I think it is a problem that SQLExecDirectW() returns SQL_SUCCESS even if sql finishes with error.
>
>
> Regards,
> Ryohei Takahashi


pgsql-odbc by date:

Previous
From: "Inoue, Hiroshi"
Date:
Subject: Re: Problem compiling in mac os with unix odbc
Next
From: Tom Lane
Date:
Subject: Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error