X hits on this document

372 views

0 shares

1 downloads

0 comments

100 / 142

XML and MySQL

  • mysql --xml -u root waters < get-waters-03.sql

  • mysql --xml -u root waters < get-waters-04.sql

  • mysql --xml -u root waters < get-waters-and-collectors-01.sql

  • mysql --xml -u root waters < get-waters-and-collectors-02.sql

  • mysql --xml -u root waters < get-waters-and-collectors-03.sql

As before, it is possible save the output of these commands to text files and manipulate them using XSLT.

Databases, especially relational databases, are the electronic tool to use to manage lists of things. Lists of employees. Lists of books. Lists of Internet resources. Relational databases are not well suited for managing the content of narrative texts such as the content of books or journal articles. Yes, it is good for describing books and journals, but not managing the book's content itself. It is too difficult to create descrete parts of books. Chapters? Sections? Paragraphs? Sentences? Words? Databases are good at managing lists of things because they excel at the ability of editing specific aspects of a list.

In the form of a report XML is a pretty good way to represent the content of a database, but it does not lend itself very well to editing. There are a few "native XML databases" available supporting querying and updating of XML documents as a whole. A good example is Sleepycat Software's Berkeley DBXML, but few of these native databases seem to be taking the XML world by storm. Time will tell whether or not XML documents can be manipulated in the same way relational database content is ma- nipulated, but right now XML seems to be firmly planted more as a reporting format as opposed to a format for repeated editing.

92

Document info
Document views372
Page views378
Page last viewedSat Dec 03 12:45:08 UTC 2016
Pages142
Paragraphs3126
Words34660

Comments