在灵活的内容数据库中存储的XML [英] Storing XML in a Database for Flexible Content

问题描述

我正在构建从几个不同的RSS聚合内容供稿和API，把它存储，然后用基于内容的来源上是唯一的格式输出它的系统。我目前的计划是创建一个XML结构为每一个​​独特类型，存储使用该结构在MySQL数据库中的每个记录，然后检索它并适当地分析它的显示。

I'm working on building a system that aggregates content from several different RSS feeds and API's, stores it, and then outputs it with unique formatting based on the source of the content. My current plan is to create an XML structure for each unique type, storing each record using that structure in a MySQL database, and then retrieving it and parsing it appropriately for display.

有没有使用此方法的任何显著的问题，还是有更好的方法来达到同样的目标？

Are there any significant issues to using this approach, or are there better ways to achieve the same goal?

推荐答案

XML数据库中的大约是铁梁灵活。它几乎成为无unqueryable数据库支持，而且当时是不是特别快。打破它，它正常化，按常规存放地。

XML in a database is about as flexible as an iron girder. It becomes practically unqueryable without database support, and even then it isn't particularly fast. Break it down, normalize it, and store it as conventionally as possible.

这篇关于在灵活的内容数据库中存储的XML的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！