See the Mailing Lists Page for how to subscribe and unsubscribe.
eprints_tech messages
Please note: this page shows emails that have been sent to the eprints_tech mailing list. Some of these may be spam emails we have failed to filter.
Re: [EP-tech] Re: eprints3.1 install error
From: Tim Brody <tdb01r AT ecs.soton.ac.uk>
Date: Thu, 08 May 2008 14:44:50 +0100
| Threading: | • This Message → Re: [EP-tech] Re: eprints3.1 install error from emrekiziltas AT sabanciuniv.edu |
*** http://www.eprints.org/tech.php/id/%3C482303D2.1080704%40ecs.soton.ac.uk%3E *** EPrints community wiki - http://wiki.eprints.org/ Emre Kızıltaş wrote: > *** > ↵ http://www.eprints.org/tech.php/id/%3C4822FC83.9020906%40sabanciuniv.edu%3E > > *** EPrints community wiki - http://wiki.eprints.org/ > > Hi >> >> We have eprints3.0.1 and we want to see eprints 3.1.So I ve just >> configured source to different directory and after then i try to use >> epadmin. >> When i run epadmin ,i get this error at the begining of creating >> database.Is there anybody was faced with this problem. >> >> DBD::mysql::db do failed: Row size too large. The maximum row size >> for the used table type, not counting BLOBs, is 65535. You have to >> change some columns to TEXT or BLOBs at >> /var/lib/eprints3.1/perl_lib/EPrints/Database.pm line 2953. >> SQL ERROR (do): CREATE TABLE `eprint__ordervalues_en` (`eprintid` >> integer NOT NULL, `rev_number` varchar(255), `documents` >> varchar(255), `eprint_status` varchar(255), `userid` varchar(255), >> `importid` varchar(255), `source` varchar(255), `dir` varchar(255), >> `datestamp` varchar(255), `lastmod` varchar(255), `status_changed` >> varchar(255), `type` varchar(255), `succeeds` varchar(255), >> `commentary` varchar(255), `replacedby` varchar(255), >> `metadata_visibility` ......... I think this is a bug. In perl_lib/EPrints/Database.pm:create_dataset_ordervalues_tables change "text" to "longtext". Cheers, Tim.
[index] [prev] [next] [options] [help]