2 Mar 14, 2005 03:39
It's a MySQL issue, rather than a b2evolution issue. Each post is saved in a single field in a table called evo_posts. There is a limit on the number of bytes stored in a single text field.
I realize that your project is currently using post pages to simulate manuscript pages, but from a database efficiency point-of-view, it would be better to have each page be in a separate field (or post) rather than just crammed into one.
A quick search on "mysql text field limitation maximum bytes" has yielded [url=http://simon.incutio.com/archive/2002/08/01/mysqlTextLimits]this page[/url] which says:
MySQL text limits
Today's scary discovery: MySQL TEXT fields have a limit of 65,000 bytes. If you insert anything larger than that in to a normal TEXT field mySQL will silently truncate your data without telling you (meaning software checks are probably a good idea). MEDIUMTEXT will store 16 million characters and LONGTEXT can handle over 4 trillion, but this information does not appear to be readily available in the online mySQL manual (although it is hinted at in this table). Something to bare in mind when designing database applications.
Posted 1st August 2002 - 12:24 | Categories: PHP, Open Source
I'd recommend in your back office "settings" tab - display only one post per page, archive on a post-by-post basis. You could even give your post titles chaper & page numbers and then the archive would be a list of pages.
Hope this helps. Sounds like an interesting project.