Good points. Justin
on 14/06/03 1:52 PM, Robert Cummings ([EMAIL PROTECTED]) wrote: > I you don't expect to do much with the data then I would recommend using an > SQL table since then you can easily search on all of the fields. Later if you > find you have more needs then conversion to XML will be trivial. Regardless > of which route you take if speed is an issue you can always cache either the > parsed XML or the SQL query results. It doesn't make much difference. > > Cheers, > Rob. > > Justin French wrote: >> >> Hi all, >> >> I'm looking at a site where there will be a lot of articles, all of which >> will be added once, and rarely edited again... >> >> Let's say each article consisted of 6 data types: >> - id >> - author >> - authorEmail >> - datePublished >> - introduction >> - bodyText >> >> I'm considering: >> >> a) storing this data in a MySQL table (a fairly simple query) >> b) storing this data in a pseudo XML format like: >> >> <id>24</id> >> <author>Justin French</author> >> <author_email>[EMAIL PROTECTED]</author_email> >> <date_published>2003-11-28</date_published> >> <intro>This is my intro</intro> >> <body>This is my text and html -- say 1000 words?</body> >> >> I plan on doing my own performance tests, but I'd love to hear any opinions >> about which would form of data retrieval would cause less of a performance >> burden on the server (MySQL is on the same box as the htdocs and apache). >> >> TIA, >> >> Justin >> >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
