*shrug* I'm only using MySQL right now. "Bill Schneider" <[EMAIL PROTECTED]> writes:
> Thanks. I found the patches to db.props on the mail-archive but not the > discussion. It looks like this allows you to use the type VARBINARY which > maps to Postgres BYTEA and Oracle LONG RAW, but not the BLOB (OID, BLOB) > type. > > Is there a good reason to use VARBINARY instead of BLOB? Or is this just > too db-specific to make a good generalization? > > -- Bill > >> 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 <[EMAIL PROTECTED]> 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: -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
