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.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
