Hello all, Thanks much for your replies.
OK, so I realized that I may not have explained the problem clearly enough. I will try to do it now. I am a researcher in computational linguistics, and I am trying to research language usage and writing styles across different genres of books over the years. The system I am developing is not just to serve up e-book content (that will happen later possibly) but to help me analyze at micro-level the different constituent elements of a book ( say at chapter level or paragraph level). As part of this work, I need to break-up, store and repeatedly run queries across multiple e-books. Here are several additional sample queries: * give me books that use the word "ABC" * give me the first 10 pages of e-book "XYZ" * give me chapter 1 of all e-books Definitely, at a later stage when I start making my research available to the community, I will need to be able to provide fulltext (or chapter-wise) search also to the users, among other things. Please let me know if you have additional comments. Andy On Thu, Jun 10, 2010 at 9:05 PM, Peter Chacko <peterchack...@gmail.com>wrote: > Usually, you better use a NAS for such purpose. Database is designed > to store highly transactional, record oriented storage that needs fast > access... You can look for any Enterprise content management systems > that rest its storage on a scalable NAS, with file virtualization in > the long run. > > thanks > > On Fri, Jun 11, 2010 at 8:04 AM, SHAWN L.GREEN <shawn.l.gr...@oracle.com> > wrote: > > On 6/10/2010 10:16 PM, Andy wrote: > >> > >> Hello all, > >> > >> I am new to MySQL and am exploring the possibility of using it for my > >> work. > >> I have about ~300,000 e-books, each about 100 pages long. I am first > going > >> to extract each chapter from each e-book and then basically store an > >> e-book > >> as a collection of chapters. A chapter could of course be arbitrarily > long > >> depending on the book. > >> > >> My questions are: > >> > >> (1) Can MySQL handle data of this size? > >> (2) How can I store text (contents) of each chapter? What data type will > >> be > >> appropriate? longtext? > >> (3) I only envision running queries to extract a specific chapter from a > >> specific e-book (say extract the chapter titled "ABC" from e-book number > >> XYZ > >> (or e-book titled "XYZ")). Can MySQL handle these types of queries well > on > >> data of this size? > >> (4) What are the benefits/drawbacks of using MySQL compared to using XML > >> databases? > >> > >> I look forward to help on this topic. Many thanks in advance. > >> Andy > >> > > > > Always pick the right tool for the job. > > > > MySQL may not be the best tool for serving up eBook contents. However if > you > > want to index and locate contents based on various parameters, then it > may > > be a good fit for the purpose. > > > > Your simple queries would best be handled by a basic web server or FTP > > server because you seem to want > > > > http://your.site.here/ABC/xyz > > > > where ABC is your book and xyz is your chapter. > > > > Those types of technology are VERY well suited for managing the > repetitive > > streaming and distribution of large binary objects (chapter files) like > you > > might encounter with an eBook content delivery system. > > > > -- > > Shawn Green > > MySQL Principle Technical Support Engineer > > Oracle USA, Inc. > > Office: Blountville, TN > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: > > http://lists.mysql.com/mysql?unsub=peterchack...@gmail.com > > > > >
