patch to db.props for postgres

[Bill Schneider <bs...@vecna.com>]

It seems like the JDBC BLOB type which creates a BLOB column on Oracle 
should create an OID column in PostgreSQL.  Even though the Postgres 
JDBC  driver's handling of OID columns is somewhat broken 
(ResultSet.getBlob() returns a java.sql.Blob OK, but getObject() returns 
a java.lang.Integer!) we can at least generate SQL that creates the 
table without a parse error:

-- Bill

================== tear here
--- src/templates/sql/base/postgresql/db.props	16 Feb 2002 18:25:01 -0000	
1.3
+++ src/templates/sql/base/postgresql/db.props	18 Feb 2002 17:56:00 -0000
@@ -28,7 +28,7 @@
  DISTINCT =
  STRUCT =
  ARRAY =
-BLOB =
+BLOB = oid
  CLOB = text
  REF =


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: patch to db.props for postgres

[Daniel Rall <dl...@finemaltcoding.com>]

Hey Bill, you might want to search the mailing list archive (link at
the bottom of this message) for Colm and Rhys' discussion of this very
problem.  They managed to come up with a clean solution, and the
db.props has been updated in the stand-alone repo.

Bill Schneider <bs...@vecna.com> writes:

> It seems like the JDBC BLOB type which creates a BLOB column on Oracle
> should create an OID column in PostgreSQL.  Even though the Postgres
> JDBC  driver's handling of OID columns is somewhat broken
> (ResultSet.getBlob() returns a java.sql.Blob OK, but getObject()
> returns a java.lang.Integer!) we can at least generate SQL that
> creates the table without a parse error:
>
> -- Bill
>
> ================== tear here
> --- src/templates/sql/base/postgresql/db.props	16 Feb 2002 18:25:01 -0000	
> 1.3
> +++ src/templates/sql/base/postgresql/db.props	18 Feb 2002 17:56:00 -0000
> @@ -28,7 +28,7 @@
>   DISTINCT =
>   STRUCT =
>   ARRAY =
> -BLOB =
> +BLOB = oid
>   CLOB = text
>   REF =

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>