Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---------------------------------------------------------------------------
Nicolas Verger wrote:
> > > 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, skipping... ]
[ Attachment, skipping... ]
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026