Thanks for your reply Eric, Yeah, the Image column type might be a better choice here. I was tracing through the Turbine code today and noticed in the BasePeer.insertOrUpdateRecord() method seems to be the point at which it hands off to Village to do the update.
There doesn't seem to be any use of the setValue(Object) type method you described (within village) just byte[] (amoung the other types). We're you able to use Peers with the blobs? If so, what did your doBuild() method of your generated MapBuilder class look like? Thanks again for your reply. cheers, Paul Smith -----Original Message----- From: Eric Pugh [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 1:42 AM To: 'Turbine Users List' Subject: RE: BasePeer, byte[], BLOBs Part II I was able to store blobs in MSSql server using the sun jdbc-odbc bridge.. I believe, but am not positive, that if you are using the MS JDBC driver, then the column has to be type Image, and the tool has to use setObject not setBlob.. Of course, this type of thread keeps coming up over and over, but I haven't had a chance to work through it.. I would love to hear the result though! Eric -----Original Message----- From: Paul Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 7:37 PM To: Turbine Users List (E-mail) Subject: BasePeer, byte[], BLOBs Part II Sorry for that premature Post... Anyway, the doBuild goes something like this: String string = new String(""); Integer integer = new Integer(0); dbMap = TurbineDB.getDatabaseMap(); byte[] blob = new byte[1]; dbMap.addTable(getTable()); TableMap tMap = dbMap.geTable(getTable()); ..... tMap.addColumn( getToolkitFactory_BLOB(), blob, Integer.MAX_VALUE ); I've tried several different approaches, even initialising the byte[] size with Interge.MAX_VALUE but that of course gives me an OutOfMemory error. Otherwise I get the error from SQL Server JDBC saying "String or binary data would be truncated". Can someone point me to a resource, or file me in on how BasePeer/BLOB's work together? cheers, Paul Smith -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
