This is a multi-part message in MIME format.
------_=_NextPart_001_01C8BC3C.971DD00D
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello PostgreSQL XML Experts,
=20
I was exploring xml sup****t in postgreSQL and ran into few questions
answer to which I couldn't find easily in the do***entation. I would
appreciate responses to following queries:
=20
1) Can xml column be constrained to be DO***ENT or CONTENT type?
XMLPARSE/XMLSERIALIZE functions allows to set XML option DO***ENT or
CONTENT type. Can we do the same when defining an xml column level?
2) Is there plan in near future to sup****t XML schema validation
i.e to ensure inserted xml do***ent conforms to a preregistered set of
XML schemas.
3) Sup****t for XQuery - I know it is asking for too much but when
do you see it happening in the future.=20
4) Sup****t for xml indexes - Is it something that is being worked
upon for next release?
=20
Our application sup****t many underlying databases and I would hate to
list out the stuff users cannot do when using xml datatype in
postgresql. So far for non-xml functionality we haven't had to this and
I hope I don't need to do it for xml as well.
=20
Thanks,
Brijesh
=20
=20
------_=_NextPart_001_01C8BC3C.971DD00D
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40"
=
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/"
xmlns:D=3D"DAV:" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml"
=
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/"
=
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/"
=
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#"
=
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp"
=
xmlns:udc=3D"http://schemas.microsoft.com/data/udc"
=
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"
=
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"
=
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/"
=
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/"
=
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
=
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"
=
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/"
=
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
=
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relation****=
ps" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
=
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@[EMAIL PROTECTED]
15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
..MsoChpDefault
{mso-style-type:ex****t-only;}
@[EMAIL PROTECTED]
Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@[EMAIL PROTECTED]
l0
{mso-list-id:447621612;
mso-list-type:hybrid;
mso-list-template-ids:-851643692 67698705 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@[EMAIL PROTECTED]
l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal>Hello PostgreSQL XML Experts,<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>I was exploring xml sup****t in postgreSQL and ran =
into few questions
answer to which I couldn’t find easily in the do***entation. I =
would
appreciate responses to following queries:<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoListParagraph =
style=3D'margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !sup****tLists]><span =
style=3D'mso-list:Ignore'>1)<span
style=3D'font:7.0pt "Times New Roman"'> =
</span></span><![endif]>Can
xml column be constrained to be DO***ENT or CONTENT type?<o:p></o:p></p>
<p class=3DMsoListParagraph =
style=3D'margin-left:.25in'>XMLPARSE/XMLSERIALIZE
functions allows to set XML option DO***ENT or CONTENT type. Can we do =
the same
when defining an xml column level?<o:p></o:p></p>
<p class=3DMsoListParagraph =
style=3D'margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !sup****tLists]><span =
style=3D'mso-list:Ignore'>2)<span
style=3D'font:7.0pt "Times New Roman"'> =
</span></span><![endif]>Is
there plan in near future to sup****t XML schema validation i.e to ensure
inserted xml do***ent conforms to a preregistered set of XML =
schemas.<o:p></o:p></p>
<p class=3DMsoListParagraph =
style=3D'margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !sup****tLists]><span =
style=3D'mso-list:Ignore'>3)<span
style=3D'font:7.0pt "Times New Roman"'> =
</span></span><![endif]>Sup****t
for XQuery – I know it is asking for too much but when do you see =
it happening
in the future. <o:p></o:p></p>
<p class=3DMsoListParagraph =
style=3D'margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !sup****tLists]><span =
style=3D'mso-list:Ignore'>4)<span
style=3D'font:7.0pt "Times New Roman"'> =
</span></span><![endif]>Sup****t
for xml indexes – Is it something that is being worked upon for =
next
release?<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Our application sup****t many underlying databases =
and I
would hate to list out the stuff users cannot do when using xml datatype =
in
postgresql. So far for non-xml functionality we haven’t had to =
this and I
hope I don’t need to do it for xml as well.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Thanks,<o:p></o:p></p>
<p class=3DMsoNormal>Brijesh<o:p></o:p></p>
<p class=3DMsoListParagraph><o:p> </o:p></p>
<p class=3DMsoListParagraph><o:p> </o:p></p>
</div>
</body>
</html>
------_=_NextPart_001_01C8BC3C.971DD00D--
|
