Patch : Re: JDBC improvements

From: "Nicolas Verger" <nicolas(at)verger(dot)net>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Patch : Re: JDBC improvements
Date: 2001-12-07 09:45:05
Message-ID: OBEKKEAKKLKKGIEBIPICAEGFCCAA.nicolas@verger.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers 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 Content-Type Size
patch_warnings.zip application/x-compressed 7.5 KB
InterScan_SafeStamp.txt text/plain 170 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Turbo Fredriksson 2001-12-07 10:32:46 restoring a shadow
Previous Message Hiroshi Inoue 2001-12-07 09:08:32 Re: Second call for platform testing

Browse pgsql-jdbc by date

  From Date Subject
Next Message Paul Wallace 2001-12-07 10:32:57 JDBC classes?
Previous Message Mike Cannon-Brookes 2001-12-07 05:23:30 Re: Problems with truncated BLOB