> XML in files, and not in DB is fine for small site, or if you do not > have a lot of consent turn over. > > But it is much easier to operate a large site, whit a lot of > approval, > editing, etc. and complex custom layouts (tiles) if you store XML > content in a db, IMO. Ex: flag content as approved. Count number of > clicks on it. Display content to a role. etc. is trivial with > a DB XML.
Well, the question is to know what change most. The XML content itself or the metadata around it. The advantage of DB is the notion of relations. The drawback is the cache management. If the DB allows to retrieve timestamps or things like that so you can take decisions about cache, it's fine. Filesystem can be a VERY efficient database, when properly used. My main problem with XML databases is the poor load capability. And RDBMS with XML extensions have too poor functionnalities (at least Oracle 9iR2) This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
