It sounds like ths number of dc:relation fields in DC might be in general problematic then? I can see this being an issue also in terms of object serialisation/deserialisation as DC is inline, something that http://www.fedora-commons.org/jira/browse/FCREPO-492 might address?
However changing the interpretation of "text" to LONGTEXT for MySQL would at least be consistent with the datatypes of other SQL databases. Steve > -----Original Message----- > From: Aaron Birkland [mailto:[email protected]] > Sent: 23 April 2010 14:43 > To: Steve Bayliss > Cc: 'Caleb Derven'; [email protected] > Subject: Re: [Fedora-commons-users] StorageDeviceException errors > > > Long text fields are problematic all around. In PostgreSQL, > text fields > van be any length up to what can be addressed by a 32 bit integer - in > the gigabyte range. However, *indexing* these is another matter. I > think mysql silently truncates index entries. Postgresql > will throw an > error. I think the postgresql limit is roughly 1/4 to 1/3 > the page size > (which by default is 8K). So anything over 2000 characters > is drifting > into trouble area. > > In any case, the field search index basically becomes meaningless with > large text fields, and in cases like this, becomes actively harmful. > > > -Aaron > > > > It looks like you might be hitting the MySQL TEXT field > size limit of > > 2^16 bytes (65536). Altering the column type should solve this, to > > MEDIUMTEXT or LONGTEXT. You would have to do this manually. > > Alternatively you could look at using a database that doesn't have > > this limitation for TEXT fields (PostgreSQL I believe has > an unlimited > > TEXT field length). > > > > ------------------------------------------------------------------------------ _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
