Hi Bill, I don't think this has got anything to do with torque. It's most probably the JDBC libraries that you are using. I had similar issues with my JDBC code a year back. The database we used was Oracle 8i. Oracle does not support storing of CLOBs having size greater than 4000 bytes. So if the large object's size goes beyond 4000 bytes the DB will implicitly store the data at some location whose refernce is then attached to your row's clob column for you to locate it. I could overcome this problem using the Oracle's CLOB implementation as opposed to java.sql.CLOB. May be you too should give it a try. Hope this helps.
-PP > -----Original Message----- > From: Bill Schneider [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 29, 2003 2:01 AM > To: Turbine Torque Users List > Subject: Torque and LOBs > > > I'm testing to see if I can get Torque to support large objects across > different databases focusing on PostgreSQL and Oracle right now. I've > noticed two things: > > In Oracle (9.2): inserts into CLOBs and BLOBs in work right > out of the box, > but for some reason, CLOB columns are "null" after a select. > > In PostgreSQL (7.3): major problems trying to get LOB > insertion to work. > First ran into trouble because JDBC driver metadata returns > "Types.INTEGER" > for columns of type "oid" rather than VARBINARY. Patched the > JDBC driver to > return VARBINARY, but now have another problem: PostgreSQL is > returning > > "ERROR: oidin: error in "string": can't parse "string"" > > on closer inspection inside the JDBC driver somehow the > byte[] got turned > into a String. Any ideas how that could have happned? > > Anyone successful using PG + Torque + large objects? > > -- Bill > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
