Hmmm, I can now totally reproduce it, we're meeting the 4k limit of BLOB update type, but for BLOB column now, LONG RAW is already patched.
I've never met it cause my profiles where smaller than 4k, and the "trick" used for LONG RAW (stmt.setBinaryStream for those who knows), ISN'T working in the particular case of Blob and oracle, nice :) Although this seems to be a common issue, just search for 4k update blob oracle. BTW, you were right, we first have to crete a null blob in the table (specific to Oracle), then update it with the real one, very easy... I'll try to come up with a patch for village, as it is village who is doing the update. Aurelien Hoffman, Randy a �crit : > I appreciate the input. I can reproduce it at will, but just for > blob, long raw works fine. I create a new user which logs me in. As > soon as I minimize a portlet I check the value of profile, it is > null. Very odd. > > thanks, > > randy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
