Patch : Re: JDBC improvements - Mailing list pgsql-jdbc

From Nicolas Verger
Subject Patch : Re: JDBC improvements
Date
Msg-id OBEKKEAKKLKKGIEBIPICAEGFCCAA.nicolas@verger.net
Whole thread Raw
In response to Re: [HACKERS] JDBC improvements  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Patch : Re: JDBC improvements
Re: Patch : Re: JDBC improvements
List pgsql-jdbc
> > Ok, the getWarnings() method works on the Connection but not on
> the Statment
> > nor ResultSet... Why ?
> > I look in the source and it's just a little patch to do it.
> > I'm not used in GPL licence so if I make this patch what may I
> do with it ?
> >
> > I watched for cancel query too, and I may work on it too ...
>
> We are BSD license.  Is that what you meant?  Sure, send it over to jdbc
> list or patches list.

Ok, so I send the first patch. It correct the propagation of the SQLWarnings
to the Statement and the ResultSet

Change are :
Add method addWarnings(SQLWarning) into org.postgresql.ResultSet
Add method addWarning(String) into org.postgresql.Statement
Modify method execute() into org.postgresql.core.QueryExecutor
    - Clear the warning of the current statement before process the query
    - Set the new warnings to the statement too
    - Add the statement warning to the ResultSet when the query is processed


Attachment

pgsql-jdbc by date:

Previous
From: "rasejo"
Date:
Subject: Encoding
Next
From: Hannu Krosing
Date:
Subject: Re: [HACKERS] [GENERAL] java stored procedures