assuming this is for books/pages to be displayed on line...
how about if you just keep just important stuff in mysql
like chapter titles and how many pages the book has, author, edition,
etc....
then you keep files for each page (or book) in the filesystem - xml,
txt, etc - and you just make a pagination navigation (and styling)
depending of the book's number of pages, chapters, etc...
since book's contents don't change you don't need that as dynamic data....
if they have to download the whole book make them into pdfs. or
something....
Khaled al-Horani wrote:
Hello,
I'm building a web application for a library but I faced a problem ...
NOTICE: This web app includes a feature that you can read the books online
...
I have to save the books either in the database (mysql for sure) or on the
hard disks ...
but I preferred DB choice because of many befits (search, speed, time and
many others) ...
The problem is how to save the book, till now I have three choices:
1- save the whole book in one record of type long text (downside is the
bandwidth ,,, it requires a lot of bandwidth to transfer the whole book to
the user)
2- save each chapter of each book in a record
3- save each page of each book in one record (the downside is the huge
amount of records but the benefits are saving bandwidth and easier
pagination)
I prefer the third choice but is mysql capable of handling this huge amount
of records (it maybe be millions because I have over 10,000 book)
thanks in advanced
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
