[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser, but there is
lots of
Hannu Krosing wrote:
[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser,
[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser, but there is
lots
I have been planning to test the whole thing with a few .NET
applications. I am currently using expat to parse the output to ensure
that it all works correcty.
That, unfortunately, probably implies that your implementation is almost
totally non-interoperable.
You should put out of your
On Thu, Apr 03, 2003 at 07:54:13AM -0500, [EMAIL PROTECTED] wrote:
I have been planning to test the whole thing with a few .NET
applications. I am currently using expat to parse the output to ensure
that it all works correcty.
That, unfortunately, probably implies that your
mlw kirjutas T, 01.04.2003 kell 15:29:
Hannu Krosing wrote:
[EMAIL PROTECTED] kirjutas E, 31.03.2003 kell 19:52:
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned.
Did you read the SOAP spec ?
yes
???
Hannu Krosing wrote:
mlw kirjutas T, 01.04.2003 kell 15:29:
Hannu Krosing wrote:
[EMAIL PROTECTED] kirjutas E, 31.03.2003 kell 19:52:
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned.
Did you read
Andrew Dunstan writes:
If the intention is to use field names as (local) tag names, how will you
handle the case where the field name isn't a valid XML name? Of course, one
could do some sort of mapping (replace illegal chars with _, for example)
but then you can't be 100% certain that you
mlw writes:
That function looks great, but what happens if you need to return 1
million records?
The same thing that happens with any set-returning function: memory
exhaustion.
I have an actual libpq program which performs a query against a server,
and will stream out the XML, so the number
mlw kirjutas K, 02.04.2003 kell 15:56:
Hannu Krosing wrote:
What you have come up with _is_not_ a SOAP v1.1 message at all. It does
use some elements with similar names but from different namespace.
the SOAP Envelope, Header and Body elemants must be from namespace
Hannu Krosing wrote:
mlw kirjutas K, 02.04.2003 kell 15:56:
Hannu Krosing wrote:
What you have come up with _is_not_ a SOAP v1.1 message at all. It does
use some elements with similar names but from different namespace.
the SOAP Envelope, Header and Body elemants must be from namespace
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser, but there is
lots of room to be flexible.
This is /exactly/ the standard problem
Hannu Krosing wrote:
[EMAIL PROTECTED] kirjutas E, 31.03.2003 kell 19:52:
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned.
Did you read the SOAP spec ?
yes
The description of the fields
isn't the actual data
Out of curiousity, what is the purpose of putting the qry:ROWSET
description into the message at all (header or not)? Isn't it a
perfectly valid SOAP message (and just as parseable) with that removed?
I freely admit to not being a soap expert, but similar SOAP
messages I generate from queries
PROTECTED]
To: mlw [EMAIL PROTECTED]
Cc: Hannu Krosing [EMAIL PROTECTED]; [EMAIL PROTECTED];
Postgres-hackers [EMAIL PROTECTED]
Sent: Tuesday, April 01, 2003 12:40 PM
Subject: Re: [HACKERS] PostgreSQL and SOAP, suggestions?
Out of curiousity, what is the purpose of putting the qry:ROWSET
description
I can certainly imagine cases for processing where having the field
names and other metadata up front (maybe add type info, nullable, etc
instead of just undefined) would be useful.
here's another question:
If the intention is to use field names as (local) tag names, how will
you
mlw writes:
Given a HTTP formatted query:
GET http://localhost:8181/pgmuze?query=select+*+from+zsong+limit+2;
The output is entered below.
That looks a lot like the SQL/XML-style output plus a SOAP header. Below
is the output that I get from the SQL/XML function that I wrote. A simple
XSLT
That function looks great, but what happens if you need to return 1
million records? Wouldn't you exhaust all the memory in the server? Or
can you stream it somehow?
I have an actual libpq program which performs a query against a server,
and will stream out the XML, so the number of records
mlw kirjutas E, 31.03.2003 kell 03:43:
Given a HTTP formatted query:
GET http://localhost:8181/pgmuze?query=select+*+from+zsong+limit+2;
The output is entered below.
Questions:
Is there a way, without spcifying a binary cursor, to get the data types
associated with columns? Right now I
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned. The description of the fields
isn't the actual data retrieved, so it doesn't belong in the body, so it
should go into the header.
mlw kirjutas E, 31.03.2003 kell 03:43:
Given
[EMAIL PROTECTED] kirjutas E, 31.03.2003 kell 19:52:
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned.
Did you read the SOAP spec ?
The description of the fields
isn't the actual data retrieved, so it doesn't belong in the
Given a HTTP formatted query:
GET http://localhost:8181/pgmuze?query=select+*+from+zsong+limit+2;
The output is entered below.
Questions:
Is there a way, without spcifying a binary cursor, to get the data types
associated with columns? Right now I am just using undefined, as the
ODBC version
22 matches
Mail list logo
