Re: Interpretability with xDBC specification - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Interpretability with xDBC specification
Date
Msg-id AANLkTinBS8Ixk9cRB3UoCPqeOl9081u8Hg3qF94FHRyD@mail.gmail.com
Whole thread Raw
In response to Re: Interpretability with xDBC specification  ("Sumit Pandya" <sumit.pandya@elitecore.com>)
Responses Re: Interpretability with xDBC specification  (Lew <noone@lewscanon.com>)
List pgsql-jdbc
On Tue, Jul 6, 2010 at 7:30 AM, Sumit Pandya <sumit.pandya@elitecore.com> wrote:
> Dave,
>        I could not find any message on topic of such generic level of JDBC
> compliance which can lead to higher interpretability. Understand my
> perspective of mail is neither of PostgreSQL USER and nor of setQueryTimeout
> issue.
>        I made a generic suggestion which give higher adaptability to people
> who are willing to migrate to PostgreSQL. That will be first step towards
> increasing PostgreSQL community. I believe that clarify my intent properly.
>
Sumit,

My reference was to exactly the setQueryTimeout discussion, not a
general discussion. As Oliver pointed out, please tell us what is not
compliant so that we can address this.

It is my experience that "compliant" means the way that "XYZ" does it.
The spec is very vague in many areas so there is lots of room for
interpretation. This makes it difficult to be compliant.

Dave

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Interpretability with xDBC specification
Next
From: "Sumit Pandya"
Date:
Subject: Re: Interpretability with xDBC specification