Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error

From: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>
To: "Takahashi, Ryohei" <r(dot)takahashi_2(at)jp(dot)fujitsu(dot)com>
Cc: "'pgsql-odbc(at)postgresql(dot)org'" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error
Date: 2018-11-01 23:59:52
Message-ID: 676c0898-375d-ddad-3a70-4528b4165b82@dream.email.ne.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Tom Lane 2018-11-02 02:50:09 Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error
Previous Message Inoue, Hiroshi 2018-11-01 23:49:38 Re: Problem compiling in mac os with unix odbc