On Fri, Dec 4, 2009 at 11:51 AM, Peter Karunyu <pkarunyu@gmail.com> wrote:

Aki, here's the interesting part, you can save and output XML to and from mysql!
I can't think of any reason one would want to do that, but that didn't stop MySQL AB in having it in 5.1

@Peter, thnks for the info. :-)

 

The issue I have with using Dbs is network resources. Or if the close connection is written into a page exit, as you know end users, they will minimize the page and forget it there for a few days.... Memory is not a big deal these days, so loading an XML into memory for parsing ( hehehe...... I'm still a learner ), was not an issue. With MS Xlinq, it is even much faster to query. The other problem I have with using a Db is backups. On XML, I can create the app to create, write,read a file say in eg C:/ . I can then create an autoscript to save this file on regular intervals ( long term plan ). Ok, those who are Db gurus, what is the backup procedure for Dbs and can it be automated?

 

Finally, the security exploits of writing bad queries in sql based system is a concern.

 

I guess for very large apps, Dbs are necessary. But as a hobbyist I could be wrong. :-)

 

Rgds.