[jboss-user] [jBPM] - Re: [JDBCExceptionReporter] Large Objects may not be used in auto-commit mode.

[Nick Tan]

Nick Tan [http://community.jboss.org/people/missedone] created the discussion

"Re: [JDBCExceptionReporter] Large Objects may not be used in auto-commit mode."

To view the discussion, visit: http://community.jboss.org/message/611957#611957

--------------------------------------------------------------
Thanks, 

this change bypass the "Large Objects' Error

but I currently encounter another issue about "JPA, @Lob and PostgreSQL oid", I mean with the JPA, what the 'workItemByteArray' returned actually is the oid bytearray, but not the raw content data bytearray, i'm still investigate on it..

some reference:
[1]  http://virgo47.wordpress.com/2008/06/13/jpa-postgresql-and-bytea-vs-oid-type/ http://virgo47.wordpress.com/2008/06/13/jpa-postgresql-and-bytea-vs-oid-type/
[2]  http://jdbc.postgresql.org/documentation/publicapi/org/postgresql/largeobject/LargeObjectManager.html http://jdbc.postgresql.org/documentation/publicapi/org/postgresql/largeobject/LargeObjectManager.html
[3]  http://snipplr.com/view/53917/postgres-how-to-read-oid-value-using-jdbc-api/ http://snipplr.com/view/53917/postgres-how-to-read-oid-value-using-jdbc-api/

the bottom line is, use the PostgreSQL JDBC driver to access the real data bytearray with oid, i think
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/611957#611957]

Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20110625/cc386f54/attachment-0001.html