XML is a perfect tool for storing data when you do not have a database available. My application, cfcPowerTools, uses XML for config data because cfcPowerTools does not require a database to be operational. Eventually, cfcPowerTools will be able to work against more databases then just SQL Server. Using XML as a storage medium allows cfcPowerTools to be database independent. cfcPowerTools also uses XML based on a schema to define the structure of a CFC. This guarantees consistency for CFC.
Tom -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Woodward Sent: Friday, October 28, 2005 8:49 AM To: [email protected] Subject: Re: [CFCDev] CFSQLTool debate On 10/28/05, John Farrar <[EMAIL PROTECTED]> wrote: > Again... when we use related flat file databases, you are right. XML is > difficult. But if we used something like Cache which is a native object > oriented data store then your objection is immediately obsolete. Not really--what advantage does storing the XML data in an OODBMS database have over having an XML file? Requiring people to not only use a database just to get the app even up and running, but making them use an obscure solution like Cache is utterly ridiculous. I don't care what the database can or can't do, it's not a "better" solution than a plain old XML configuration file. > What is > needed is for databases to evolve. The issue is why haven't data storage > structures matured beyond the original sql store concept in years? OODBMS have been around for years and they still haven't caught on. Do a bit of research--they're a decent solution in certain fringe cases, but they have significant drawbacks as well, which is why they haven't see widespread adoption (and may never see widespread adoption). > Related > flat files with a query language need to grow into object oriented schema > based structure. The time is come and past. There are actually XML databases > on the market. It seems to me that there would be a Machii solution that > employs the power of a XML database like cache or something. I still don't see how this makes anything better or solves any problems with using an XML file. What you're proposing sounds like a solution to a problem that doesn't exist using a technology that no one uses for numerous very good reasons. -- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
