When would you prefer to store XML in a relational database?

Possible duplicate:
Why would I like to store and process XML in a relational database?

Although this surface question appears to be a rethinking of what has already been asked, I will point out in advance that it is not. My question is not how to store or retrieve XML from a relational database. The question at hand is much more fundamental than that:

What type of data do you usually store in XML format in your database? What are your design solutions for this? Are you ready to abandon the "relational" aspect of your database by adding some parts of your model to XML advertising? Things like settings or configuration files can be stored as XML in a relational database, but should you do this?

+5
source share
6 answers

Never.

Saving data for which there is some recognizable structure as XML, and not as relational data, means giving up the power of relational algebra to work with this data.

, , , XML - / .

( , , , , , , " ". , , .)

+3

XML , , XML .

+2

, IMHO, XML - , . XML, . , , XML, .

+2

XML- :

  • , -, . SOAP- / -. .
  • , . XHTML, . xml SQL Server 2005 .
  • , . , XML . , , .
+1

xml- ( , json serialized), .

0

XML- .

  • ( , , ).

  • , .

, , , , , - ( , , ), , , maintenace - . - , , , .

0
source

All Articles