• From: Dmitry Turin <sql4-en@n...>
• To: xml-dev@l...
• Date: Tue, 23 Oct 2007 08:11:23 +0300

Michael,

MK> My experience so far of these hybrid relational/xml systems is that your
MK> problem as a user is not a lack of functionality, but an excess. There are
MK> simply too many ways of doing the same thing, and they have too many
MK> irritating differences - different sets of functions, different rules for
MK> case independence, different conventions for escaping special characters -
MK> and different (unpredictably different) performance. I find it hard to
MK> believe that this ugly hybrid of SQL and XQuery represents the future of
MK> database technology. I find databases where everything is XML (or indeed
MK> where everything is tables) much easier to work with.
+1


Dmitry Turin
SQL5      (5.5.2)  http://sql50.euro.ru
HTML6     (6.4.3)  http://html60.euro.ru
Unicode7  (7.2.1)  http://unicode70.euro.ru
Computer2 (2.0.2)  http://computer20.euro.ru

• References:
  • XQuery & Several records (instead of one xml-field)
    • From: Dmitry Turin <sql4-en@n...>
  • RE: XQuery & Several records (instead of one xml-field)
    • From: "Michael Kay" <mike@s...>
  • Re: XQuery & Several records (instead of one xml-field)
    • From: "Mukul Gandhi" <gandhi.mukul@g...>
  • Re: XQuery & Several records (instead of one xml-field)
    • From: Jim Melton <jim.melton@a...>
  • Re: XQuery & Several records (instead of one xml-field)
    • From: "Mukul Gandhi" <gandhi.mukul@g...>
  • Re: XQuery & Several records (instead of one xml-field)
    • From: Liam Quin <liam@w...>
  • RE: XQuery & Several records (instead of one xml-field)
    • From: "Michael Kay" <mike@s...>