Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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: InterScan_SafeStamp.txt
Description: text/plain (170 bytes)
Attachment: patch_warnings.zip
Description: application/x-compressed (7.5 KB)

In response to

Responses

pgsql-hackers by date

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

pgsql-jdbc by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group