On 8/22/06, Bruce Momjian [EMAIL PROTECTED] wrote:
I am still waiting for some documentation on what XML support we have,
and what we need. We can't decide on this patch until we have that.
Here is my thoughts:
http://nikolay.samokhvalov.com/2006/08/23/xml-and-relational/
(maybe too much
I am still waiting for some documentation on what XML support we have,
and what we need. We can't decide on this patch until we have that.
---
Nikolay Samokhvalov wrote:
I'll prepare some classification of differend kinds
Pavel Stehule wrote:
Hello
If there were a serious amount of demand for the SQL2003 XML features
then I wouldn't be averse to putting them in, but right now it looks
like bloat with little redeeming social value. Who other than the
submitter has asked for this? I don't even see XML listed
Tom Lane wrote:
If there were a serious amount of demand for the SQL2003 XML features
then I wouldn't be averse to putting them in, but right now it looks
like bloat with little redeeming social value. Who other than the
submitter has asked for this? I don't even see XML listed in TODO.
Peter Eisentraut [EMAIL PROTECTED] writes:
There have been inquiries about some kind of XML support every few weeks
for years now. Clearly, we need to sort out what that really means.
Agreed. We need a road map of some sort.
I'm preparing a session about that for the Toronto summit.
I'll prepare some classification of differend kinds of XML support,
including a brief overview for oracle, sql server and db2 (I'm a
person who works on that SoC project)
As for Pavel's patch, I think it's pretty complete piece of several
SQL/XML functions and could be usefull for people (e.g
Do we want this XML patch in the backend? It needs syntax support so I
don't see how it could be done in /contrib. Attached.
---
David Fetter wrote:
On Wed, Sep 28, 2005 at 04:30:54PM +0200, Pavel Stehule wrote:
Hello
Bruce Momjian pgman@candle.pha.pa.us writes:
Do we want this XML patch in the backend? It needs syntax support so I
don't see how it could be done in /contrib. Attached.
I think this could easily be done as an external module if it didn't
insist on random additions to the function-call
Peter Eisentraut wrote:
Tom Lane wrote:
I think this could easily be done as an external module if it didn't
insist on random additions to the function-call syntax. AFAICS there
isn't anything there that couldn't be done without that.
This is part of the SQL standard.
Ah, I suspected
Peter Eisentraut [EMAIL PROTECTED] writes:
This is part of the SQL standard.
[ shrug ] There is a *boatload* of new stuff in SQL2003, most of which
we probably won't ever implement. The foundation alone has enough new
cruft to keep us busy for years ... never mind stuff that shows up only
in
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
This is part of the SQL standard.
[ shrug ] There is a *boatload* of new stuff in SQL2003, most of which
we probably won't ever implement. The foundation alone has enough new
cruft to keep us busy for years ... never mind stuff
Bruce Momjian pgman@candle.pha.pa.us writes:
Do we want this XML patch in the backend? It needs syntax support so I
don't see how it could be done in /contrib. Attached.
I think this could easily be done as an external module if it didn't
insist on random additions to the function-call
Well, we have been pushing XML out of the database into side projects,
which I think is the way to go until we have an XML-standard export
format. With this one, I don't see how we can do it externally and meet
the spec. I would like to see an outline of what XML things we support
and what we
Hello
If there were a serious amount of demand for the SQL2003 XML features
then I wouldn't be averse to putting them in, but right now it looks
like bloat with little redeeming social value. Who other than the
submitter has asked for this? I don't even see XML listed in TODO.
1.
This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
David Fetter wrote:
On Wed, Sep 28, 2005 at 04:30:54PM +0200, Pavel Stehule wrote:
Hello
base type changed
On Wed, Sep 28, 2005 at 04:30:54PM +0200, Pavel Stehule wrote:
Hello
base type changed to text, better registration xmlagg function
Regards Pavel Stehule
Now with some slightly improved documentation, works vs. CVS tip as of
this writing.
Cheers,
D
--
David Fetter [EMAIL PROTECTED]
On Wed, Sep 28, 2005 at 04:30:54PM +0200, Pavel Stehule wrote:
Hello
base type changed to text, better registration xmlagg function
Interesting. The SGML docs appear to be machine-generated stubs.
Could you point to a reference for them so they can be filled in?
Cheers,
D
--
David Fetter
This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Pavel Stehule wrote:
Hello
This patch contains SQL/XML public function XMLFOREST, XMLELEMENT, ... based
on
Hello
This patch contains SQL/XML public function XMLFOREST, XMLELEMENT, ... based
on CString type. This patch hasn't high quality, but can be usefull for
testing funcionality, and maybe for some people. Patch needs initdb and
following registration:
CREATE AGGREGATE
Pavel Stehule [EMAIL PROTECTED] writes:
This patch contains SQL/XML public function XMLFOREST, XMLELEMENT, ... based
on CString type. This patch hasn't high quality, but can be usefull for
testing funcionality, and maybe for some people.
1. Why did you base the datatype on cstring? That's
Am Montag, 12. September 2005 16:05 schrieb Tom Lane:
2. Is it really necessary to hack up the grammar for this?
Yes, because the syntax defined in the SQL standard is completely weird.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
1. Why did you base the datatype on cstring? That's inappropriate for
anything except guaranteed-short strings, because it's not toastable.
It's only my laziness. I can adapt patch for TEXT. It's only temporary
solution. The goal is true xml type.
2. Is it really necessary to hack up the
22 matches
Mail list logo