I would say it depends on how much data you are going to be storing, both in terms of number of records, and number of columns/fields. If these files get to be huge, it could cause some slowing down, but if they remain small it shouldnt be too bad.
But really, the only reason you would want to use xml for a database is if you had multiple platforms/code systems etc that were going to be using it. Things will be much faster and efficient using an actual db. not to mention just the queries will be a lot easier. On 9/13/05, Will Tomlinson <[EMAIL PROTECTED]> wrote: > Hey guys, > > I'm workin' with my new cart app project and the db schema/product > options/queries are flat out insane. Looks like NASA got involved with it! > > XML looks like it'd be much more natural in structuring the data. > <item> > <id>123</id> > <color>red</color> > <size>large</size> > </item> > > etc ... etc ... > > Is there any way I can use an XML doc instead of a db for this purpose? Or > would it be just totally inefficient? > > Thanks, > Will > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:218132 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
