Hi Ryan, would you mind either creating a vtrace (http://sapdb.2scale.net/moin.cgi/VTrace) and/or supplying the table definition of MESSAGE. It would be also interesting to know how long your baMessageBody array is, to possibly be able to reproduce the issue.
Regards Alexander Schr�der SAP Labs Berlin > -----Original Message----- > From: Ryan Lissack [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 05, 2003 5:29 PM > To: [EMAIL PROTECTED] > Subject: Problems with LONG BYTE columns > > > Hi, > > We have a table with a LONG BYTE column and we are using the > JDBC driver > to update information in this table. We use a > PreparedStatement and the > setBytes (also tried setBinaryStream) method (see below) but > it appears > that the data going into the db gets truncated after about 32k. The > documentation states that columns of this type can hold up to 2 gigs. > > We are using the latest JDBC driver from the website and > version 7.3.0 > of the server. > > pstmt = m_dbConn.prepareStatement( > "update MESSAGE set body = ? where message_pk = " > + String.valueOf(nMessagePK)); > pstmt.setBinaryStream(1, new > ByteArrayInputStream(structMessageInfo.baMessageBody), > structMessageInfo.baMessageBody.length); > //pstmt.setBytes(1, structMessageInfo.baMessageBody); > pstmt.execute(); > pstmt.close(); > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
