MIME-Version: 1.0
References: <5EC17E17.7070002@anastigmatix.net>
 <CAASLQ4PAQ0PNAxJ5ad9U6o+RT2ip19FXvgoK2y1kGWaJbTZ1WQ@mail.gmail.com>
 <5ED15825.9060504@anastigmatix.net>
 <CAASLQ4OXAb+_J=oK54PH5eYuXjkV9KMsoXEcp-TYaQPqxk1Xbg@mail.gmail.com>
 <5ED270BA.9010001@anastigmatix.net> <5ED3D488.1010401@anastigmatix.net>
 <5ED474CA.3000106@anastigmatix.net>
 <CAASLQ4PfvmgKPp+aFf_r5RsBwigc+EC5Hm2CuzwJSTDCT64i-A@mail.gmail.com>
 <5ED4EA10.4030801@anastigmatix.net>
 <CAASLQ4Px21jyb2vJYSrjF5P0RqhA-G_DDWR9QHG68r+W+AqbxQ@mail.gmail.com>
 <CAASLQ4NYE-TW6hjbkSOuAY2Z4NM2cYzqSQ9ahO2LAUhdP9axeQ@mail.gmail.com>
 <5ED7E74B.9020800@anastigmatix.net>
 <CAASLQ4Od6-0=3+4ENKh1Z-Wcu5Wir-bwUn_ccO2UCmDhoR4vtQ@mail.gmail.com>
 <5EDA576E.2000204@anastigmatix.net>
 <CAASLQ4OzPwZB6GG_cXNW4WU4zpHa6wm8Q3WRWNv5pZpis+gf3w@mail.gmail.com>
 <5EDBA5D9.8090506@anastigmatix.net>
 <CAASLQ4P8e9XfUh17HFhYE4eMtq5-C4dpHQAX+hCsia-UFNAjtA@mail.gmail.com>
 <5EE7AE8C.2040201@anastigmatix.net>
 <CAASLQ4PoMTiTZUPxTR7VS8LLo9tosAMu-89T5ikWub7VbM+r4Q@mail.gmail.com>
 <5EEA6F85.9040009@anastigmatix.net>
In-Reply-To: <5EEA6F85.9040009@anastigmatix.net>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Thu, 18 Jun 2020 01:12:41 +0530
Message-ID: 
 <CAASLQ4PuYp-y8DdQPHytAcNCmR7u_th9SYYjYNB4_VM-tB5mXA@mail.gmail.com>
Subject: Re: Detecting test failures reported as warnings
To: Chapman Flack <chap@anastigmatix.net>
Cc: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000009b47a605a84cdd4e"
Precedence: bulk

--0000000000009b47a605a84cdd4e
Content-Type: text/plain; charset="UTF-8"

>
> There's a lot to like about a Java and JDBC approach. It shouldn't be hard
> to get off the ground, JDBC has a nice standard API for finding out about
> warnings (and reading through the pgJDBC code, I believe it is implemented,
> though I haven't done a test yet).
>
> Later on, as the prerequisites for migrating to TAP get accomplished,
> that code could just be evolved to match.
>
As of now, setting client log level seems to work very well. Should I try
to work out this approach or go ahead?

--0000000000009b47a605a84cdd4e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">There&#39;s a lot to like about a Java and JDBC approach=
. It shouldn&#39;t be hard<br>
to get off the ground, JDBC has a nice standard API for finding out about<b=
r>
warnings (and reading through the pgJDBC code, I believe it is implemented,=
<br>
though I haven&#39;t done a test yet).<br>
<br>
Later on, as the prerequisites for migrating to TAP get accomplished,<br>
that code could just be evolved to match.<br></blockquote><div>As of now, s=
etting client log level seems to work very well. Should I try to work out t=
his approach or go ahead?=C2=A0</div></div></div>

--0000000000009b47a605a84cdd4e--