Thanks, I wasn't but will now. Going to need something before 2007 though, or I'm in real trouble. :)
Tom
On 4/3/06, seano [EMAIL PROTECTED] wrote:
Tom,Are you following what NEHTA (National eHealth Transition Authority
www.nehta.org.au) is doing to standardise provider identification
I'd say you're far better off sticking with a database. That's what
they're designed for - especially because it sounds like there's a
fair bit of data there. What advantages would you get by using XML?
On 4/3/06, Tom MacKean [EMAIL PROTECTED] wrote:
I was all set to create a new database for
Use a database!
Use a database!!
Use a database!!!
Use a database
[EMAIL PROTECTED] 3/04/2006 10:50 am
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
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
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,
I personally also would have said db a little while ago. yet since
playing round with rss/xml i have come to the conclusion that the
easiest way to access information from ANY lanuage is xml...
and with coldfusion its a little too easy :)
sure if you have a lot of information then you need a
[EMAIL PROTECTED] wrote:
I personally also would have said db a little while ago. yet since
playing round with rss/xml i have come to the conclusion that the
easiest way to access information from ANY lanuage is xml...
Isn't this one of those fabled 'solution-seeking-problems'? What with
