Andrew Dunstan wrote:
Bruce Momjian wrote:
Are we going to publish an XML DTD for EXPLAIN, or have we already?
Not a DTD, but I am working on an XML Schema (DTDs are a bit yesterday).
Here is a RelaxNG spec which people might find a bit easier to read. It
has been autocreated by a
On Thu, Aug 20, 2009 at 9:30 AM, Andrew Dunstanand...@dunslane.net wrote:
Andrew Dunstan wrote:
Bruce Momjian wrote:
Are we going to publish an XML DTD for EXPLAIN, or have we already?
Not a DTD, but I am working on an XML Schema (DTDs are a bit yesterday).
Here is a RelaxNG spec
Andrew Dunstan and...@dunslane.net writes:
I have a couple of questions, however. First, in that long list of
alternatives for a Plan node, can any of them occur more than once?
No.
Second, we are using Item as a child of both Output and Sort-Key nodes.
Are they really describing the same
I wrote:
Andrew Dunstan wrote:
Bruce Momjian wrote:
Are we going to publish an XML DTD for EXPLAIN, or have we already?
Not a DTD, but I am working on an XML Schema (DTDs are a bit yesterday).
Here is a RelaxNG spec which people might find a bit easier to read.
It has been
Andrew Dunstan and...@dunslane.net writes:
Updated version with more complete information (regression crash was due
to my bad script).
I took a look through the source code to match it against this. I found
that you missed a couple of possibilities: we have Notify / and
Utility-Statement / as
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
Updated version with more complete information (regression crash was due
to my bad script).
I took a look through the source code to match it against this. I found
that you missed a couple of possibilities: we have Notify /
Andrew Dunstan and...@dunslane.net writes:
Tom Lane wrote:
I took a look through the source code to match it against this. I found
that you missed a couple of possibilities: we have Notify / and
Utility-Statement / as alternatives to Query just below explain.
What causes those to happen?
On Thu, Aug 20, 2009 at 12:40 PM, Andrew Dunstanand...@dunslane.net wrote:
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
Updated version with more complete information (regression crash was due
to my bad script).
I took a look through the source code to match it against
Are we going to publish an XML DTD for EXPLAIN, or have we already?
---
Andrew Dunstan wrote:
The attached tiny patch sets the explain root element for auto-explain
XML output, so it looks something like this:
Bruce Momjian wrote:
Are we going to publish an XML DTD for EXPLAIN, or have we already?
Not a DTD, but I am working on an XML Schema (DTDs are a bit yesterday).
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Andrew Dunstan wrote:
Bruce Momjian wrote:
Are we going to publish an XML DTD for EXPLAIN, or have we already?
Not a DTD, but I am working on an XML Schema (DTDs are a bit yesterday).
OK, either one would be good.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
Andrew Dunstan and...@dunslane.net writes:
Bruce Momjian wrote:
Are we going to publish an XML DTD for EXPLAIN, or have we already?
Not a DTD, but I am working on an XML Schema (DTDs are a bit yesterday).
+1 ... I asked for a spec for the output format before, and this would
do fine.
On Tue, Aug 18, 2009 at 02:11, Andrew Dunstanand...@dunslane.net wrote:
Tom Lane wrote:
Andrew Dunstan andrew.duns...@pgexperts.com writes:
The attached tiny patch sets the explain root element for auto-explain
XML output, so it looks something like this:
This looks reasonable in
The attached tiny patch sets the explain root element for auto-explain
XML output, so it looks something like this:
explain xmlns=http://www.postgresql.org/2009/explain;
Plan
Node-TypeResult/Node-Type
Startup-Cost0.00/Startup-Cost
Total-Cost0.01/Total-Cost
Andrew Dunstan andrew.duns...@pgexperts.com writes:
The attached tiny patch sets the explain root element for auto-explain
XML output, so it looks something like this:
This looks reasonable in itself, but it sort of begs the question on
two other things:
* what's the xmlns URL really going to
Tom Lane wrote:
Andrew Dunstan andrew.duns...@pgexperts.com writes:
The attached tiny patch sets the explain root element for auto-explain
XML output, so it looks something like this:
This looks reasonable in itself, but it sort of begs the question on
two other things:
* what's
Andrew Dunstan wrote:
Tom Lane wrote:
* what's the xmlns URL really going to be?
By convention it refers to a place where you publish the schema for
the document type, but it is in fact completely arbitrary, and can
refer to a non-existant resource - as long as it is unique - it's
Andrew Dunstan and...@dunslane.net writes:
One thing I definitely think we should do is to put the namespace URL in
a header file. Think of it as being a bit like the catversion.
Hardcoding it in explain.c doesn't seem like a good idea.
Well, it could at least be a #define, but what's the
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
One thing I definitely think we should do is to put the namespace URL in
a header file. Think of it as being a bit like the catversion.
Hardcoding it in explain.c doesn't seem like a good idea.
Well, it could at least be a
19 matches
Mail list logo
