Hi,
I transfer to the list to give Nicolas the opportunity to add his comments.
Michaël
-------- Message transféré --------
Sujet : Re: h2 log output
Date : Mon, 28 Dec 2015 09:28:20 +0100
De : Michaël Michaud <[email protected]>
Pour : Edgar Soldin <[email protected]>
Hi Ede,
I copied this code from PostgisFeatureInputStream where it has been
added by Nicolas in r4609.
I suppose he wanted to trace the driver name used by oj when the data
was accessed and report
the error if the desired driver was not available at that time.
I don't know why it has been added for postgis only (and now for H2, but
I have no specific argument
for H2).
Nicolas ?
Michaël
Le 27/12/2015 23:42, Edgar Soldin a écrit :
hey Mike,
any idea what the log output in the second constructor below is for and why it
is wrapped in a try/catch?
..ede
public class H2FeatureInputStream extends SpatialDatabasesFeatureInputStream {
public H2FeatureInputStream(Connection conn, String queryString) {
this(conn, queryString, null);
}
public H2FeatureInputStream(Connection conn, String queryString, String
externalIdentifier) {
super(conn, queryString, externalIdentifier);
try {
JUMPWorkbench.getInstance().getFrame().log("creating a
H2FeatureInputStream (class:" + this.getClass()
+ " ) (driver: " + conn.getMetaData().getDriverName() + ")
id"
+ this.hashCode(), this.getClass());
} catch (SQLException ex) {
Logger.getLogger(H2FeatureInputStream.class.getName()).log(Level.SEVERE, null,
ex);
}
}
------------------------------------------------------------------------------
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
