I was just repeating what I read on mysql.org. blob has a 64K limit longblob has a 4G limit
There is also something called mediumblob or something like that has a limit in between these two. The limit is therefore dependant on you data scheme and not a configuration parameter. I am not a mysql expert so I have no explanation for the different types of blobs, except a longblob takes a couple of bytes more space on your harddrive. I guess it makes sense to use blob in a database when you have a lot of small blobs, but not in a project like slide. utf8 is unicode support. It simply means that you can store filenames and properties in languages other than you server character set. This also requires an utf8 compliant client. /jacob ----- Original Message ----- From: "Ryan Rhodes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 05, 2004 3:16 PM Subject: Re: MySql-4.1-Schema.sql > Hello Jacob, > > To be honest, I'm not sure what utf8 compliance means. What could I do to > test this? > > Also, I have never worked with mysql before. Is it your understanding that > mysql has this 64k limit in other applications, and that this limit cannot > be changed through some configuration? > > Regards, > > Ryan Rhodes > > > >From: "Jacob Lund" <[EMAIL PROTECTED]> > >Reply-To: "Slide Developers Mailing List" <[EMAIL PROTECTED]> > >To: "Slide Developers Mailing List" <[EMAIL PROTECTED]> > >Subject: Re: MySql-4.1-Schema.sql > >Date: Tue, 4 May 2004 09:26:46 +0200 > > > >Hi Ryan! > > > >I used the longblob part for test some time ago and you are right - it did > >solve the problem with larger files. > >blob will set the limit to 64k and longblob will set limit to 4G. > > > >I never successfully tested the 4.1 scheme since mysql had problems on my > >machine! The big difference from 4.0 to 4.1 is the utf8 compliance. Did you > >do any testing on this part? > > > >/jacob > > ----- Original Message ----- > > From: ryan > > To: 'Slide Developers Mailing List' > > Sent: Monday, May 03, 2004 6:45 PM > > Subject: MySql-4.1-Schema.sql > > > > > > I wasn't able to use the new schema for MySql-4.1. It looks like it > >doesn't like this syntax: > > > > > > > > URI_STRING varchar(255) NOT NULL CHARACTER SET utf8 COLLATE > >utf8_general_ci, > > > > > > > > The file I attached is the schema I used to create the tables. I only > >had to move the NOT NULL part to the end of the line like this: > > > > > > > > URI_STRING varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci > >NOT NULL, > > > > > > > > Is there anyone else that has gotten this schema to work so I know it > >isn't just me? > > > > > > > > > > > > Also, Several people have posted about the MySQL Adapter not allowing > >uploads/downloads of files greater than 64k in size. I was hoping the > >upgrade to MySQL-4.1.1 would fix this but it did not. I have not seen any > >response to this, so I am including my changes to the VERSION_CONTENT table > >to fix this. The modified table uses LONGBLOB for the content field. Here > >is the full create statement from the file: > > > > > > > > CREATE TABLE VERSION_CONTENT ( > > > > VERSION_ID bigint NOT NULL, > > > > CONTENT longblob NOT NULL, > > > > PRIMARY KEY (VERSION_ID) > > > > ) TYPE=InnoDB CHARACTER SET utf8; > > > > > > > > Does anyone have any thoughts on this? > > > > > > > > Regards, > > > > > > > > Ryan Rhodes > > > > > > > >--------------------------------------------------------------------------- --- > > > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
