Thanks! I just changed it to a LONGBLOB, using: alter table revisioncontent change content content LONGBLOB;
Unfortunately, now when I do a "PROPFIND /files/" I get back a 404! :( Maybe changing the column type on an existing database wasn't such a cool thing to do. I didn't have anything important in it anyway, so I am going to recreate the database from scratch with the new column type and see if that works. You don't suppose any of the Java code actually ASSUMES that the revisioncontent column type is a BLOB as opposed to a LONGBLOB do you? On Fri, 2003-06-06 at 07:30, James Higginbotham wrote: > > You might also > > try checking the max size of the database column storing the > > data in your situation if you don't want to use the hard disk > > directly to store file contents. > > > > Ah, yes... In fact, BLOB in MySQL maxes at 64k.. You will need to use > the LONGBLOB type for the column as well. > > James > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
