Re: Public vs internal APIs

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Markus KARG <markus(at)headcrashing(dot)eu>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Public vs internal APIs
Date: 2015-07-23 18:11:15
Message-ID: CAB=Je-FThkhU+48O-HDLXNwuSOwgVXuZLSVey7F2x7dqwkCxEw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

>I mean, people shall code against java.* API, not against org.postgresql implementation. If we make this clear in the JavaDocs, maybe it is enough?

On contrary, we do want to expose advanced stuff PostgreSQL has.
For instance: "timestamp with time zone". Not everybody can upgrade to java 8.

Another example is COPY command: JDBC has no standard way of doing that.
We have to define org.postgresql interface for it.

JDBC is not that good for async operations either: logical decoding,
notify, etc, so again some org.postgresql might do much better job
here.

For regular stuff like "send int here and there", everybody should use
regular JDBC, however, there are cases when non-JDBC usage is
intended.

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Markus KARG 2015-07-23 22:05:45 Re: Public vs internal APIs
Previous Message Markus KARG 2015-07-23 17:50:23 Re: Public vs internal APIs