Message-ID: <564137A1.4060800@anastigmatix.net>
Date: Mon, 09 Nov 2015 19:17:37 -0500
From: Chapman Flack <chap@anastigmatix.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: pgsql-jdbc@postgresql.org, kdubb@me.com,
 pljava-dev@lists.pgfoundry.org
Subject: Re: more re: possible pljava / pgjdbc / pgjdbc-ng code sharing
References: <5630454F.4000900@anastigmatix.net>
In-Reply-To: <5630454F.4000900@anastigmatix.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-jdbc-owner@postgresql.org

On 10/27/15 23:47, Chapman Flack wrote:

> https://github.com/tada/pljava/wiki/Thoughts-on-logging
> ...
> My reason for writing it *now* is not that I think it's necessarily the
> most interesting, important, or pressing area needing work. Instead, I've
> written it now because I think what I've proposed might need some
> discussion and refinement, so by putting it out there early, maybe some
> of that can happen in parallel with working on other important pressing
> parts.

It turns out to be more timely than I thought - PL/Pythonu is also
developing a patch (starting last month) to the same end.

http://postgresql.nabble.com/proposal-PL-Pythonu-function-ereport-td5869255.html

On their client side, psycopg2 already exposes a documented, supported
PostgreSQL-specific Diagnostics object.

http://initd.org/psycopg/docs/extensions.html#psycopg2.extensions.Diagnostics

-Chap


-- 
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc