EPrints Technical Mailing List Archive
Message: #05872
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] MySQL 'row size too large'
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] MySQL 'row size too large'
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Date: Tue, 16 Aug 2016 08:41:23 +0000
Hi List, I am trying to add a new single value text column to our eprint table (running 3.3.12). Doing it the 'normal' way via the config seemed to break the database. Trying to add the column directly via mysql gives this error: "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" These are the details of the table: | Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | +--------+--------+---------+------------+--------+----------------+-------------+-----------------+--------------+-----------+ | eprint | MyISAM | 10 | Dynamic | 104678 | 1256 | 131511952 | 281474976710655 | 45699072 | 0 | Are there any implications in changing varchar column types to text to get round it? Cheers Mick -- Mick Eadie Research Data Management Officer University of Glasgow Tel: +44 (0) 141 330 6294 http://researchdata.gla.ac.uk | www.glasgow.ac.uk/services/datamanagement/
- Prev by Date: [EP-tech] Simple Searches and send_alerts
- Next by Date: Re: [EP-tech] Too many connections
- Previous by thread: [EP-tech] Simple Searches and send_alerts
- Next by thread: [EP-tech] REFCC plugin functionality question
- Index(es):