Yep. You can actually store a DTD in the SQL database that will
validate any XML inserted into it if you wish. I believe you can also
build very fast indices over an XML field, where a text field w/ full
text index may not be as zippy.
Chris Peterson
Gainey IT
Adobe Certified Advanced
So is there any advantage or reason I should be storing XML
data in a XML field vs. varchar??
Yes, the same reason you use other specific datatypes in SQL. The database
can validate your data, for example.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides
server CAN do, but shouldn't necessarily do?
~Brad
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 2:16 PM
To: CF-Talk
Subject: RE: MS SQL XML Datatype
So is there any advantage or reason I should be storing XML
data in a XML field vs. varchar
'variables' and stuck all my user variables into that. Just one use
where XML makes sense =)
Chris Peterson
Gainey IT
Adobe Certified Advanced Coldfusion Developer
-Original Message-
From: Brad Wood [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 3:31 PM
To: CF-Talk
Subject: RE: MS SQL
.
~Brad
-Original Message-
From: Peterson, Chris [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 3:01 PM
To: CF-Talk
Subject: RE: MS SQL XML Datatype
Brad,
I used XML to store an un-known amount of data coming from the form
scope. I wanted to, in my debug template, store any
Call me crazy, but I've just never liked the idea of storing
XML in the database in any form.
I generally agree with you, but just like almost anything else, you should
never say never. There are occasional cases where you want to store
denormalized data, and sometimes that data may be XML.
6 matches
Mail list logo
