[cfaussie] Re: OT: XML vs database

Sun, 02 Apr 2006 18:09:44 -0700

Thank you all for your replies. I will indeed use a database, use a database, use a database. (It's half built anyway).
 
I just started thinking about XML because I was looking at my iTunes library file (which is XML) and it seemed like the same sort of structure as my doctors list - that is, it's all about one particular item (song/doctor) with lots of disparate properties. 
 
Thanks,
 
Tom 
 


 
On 4/3/06, Dale Fraser <[EMAIL PROTECTED]> wrote:

XML is fine for small data sets, easy enough to parse and process using
Xpath (xmlSearch).

But for 5000, records I think a database would be better, it's quicker and
more robust, the XML model would be more appropriate for very small datasets
ie < 100 records perhaps.

With XML you have to read and parse all 5000 records every time you make and
addition or update. Ie:

1. Read all 5000 records from disk file
2. Parse all 5000 records
3. Modify XML object
4. Write all 5000 records to disk.

There are also security / locking considerations with this

Regards
Dale Fraser

> -----Original Message-----
> From: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On
> Behalf Of Tom MacKean
> Sent: Monday, 3 April 2006 10:51 AM
> To: cfaussie@googlegroups.com
> Subject: [cfaussie] OT: XML vs database
>
> I was all set to create a new database for an application that is
> basically a contact list for doctors when I thought "Would this be better
> as an XML file?". I've never used an XML file to store and retrieve data
> before, but I understand the basic concept.
>
> Let me scope it out for you:
>
> *     Doctors can have multiple addresses
> *     Addresses can have multiple doctors
> *     Doctors can have multiple provider numbers
> *     Only one person at a time needs to be able to use this application
> so locking it is fine.
> *     It doesn't have to be particularly fast
> *     There will be about 5000 doctors
>
> It seemed to me that creating <doctor> and then having multiple <address>
> and <providernumber> etc would be easier than lots of relational tables
> linked by keys.
>
> What is everyone's opinion on using XML in this way? How easy is it to
> read/filter/update data store in an XML page like this? Should I just
> stick to the db?
>
> Tom
>
>
>
> --
> IMPORTANT: This email is intended for the use of the individual
> addressee(s) named above and may contain information that is confidential
> privileged or unsuitable for overly sensitive persons with low
self-esteem,
> no sense of humor or irrational religious beliefs. If you are not the
> intended recipient, any dissemination, distribution or copying of this
> email is not authorized (either explicitly or implicitly) and constitutes
> an irritating social fauxpas. No animals were harmed in the transmission
> of this email, although the mutt next door is living on borrowed time, let
> me tell you.
>
>
> >






--
IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humor or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorized (either explicitly or implicitly) and constitutes an irritating social fauxpas. No animals were harmed in the transmission of this email, although the mutt next door is living on borrowed time, let me tell you.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~----------~----~----~----~------~----~------~--~---

Reply via email to