From: | pgsql(at)mohawksoft(dot)com |
---|---|
To: | andrew(at)dunslane(dot)net |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PostgreSQL and SOAP, suggestions? |
Date: | 2003-04-01 18:55:26 |
Message-ID: | 2577.141.154.39.187.1049223326.squirrel@mail.mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> 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 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 haven't
> generated a collision, I should think.
>
I'm not sure, I have to really research how to handle that case. I have been
simply doing a %hex translation on characters that do not conform to XML,
that may actually be "good enough(tm)."
As for the field names being undefined, if you can find a way to get the
field types without having to specify a binary cursor I'd like that.
Admitedly, I have not looked very hard. This is a small part of a bigger
project. The SQL/XML provider currently supports PG and ODBC.
The web services project, which contains the SQL/XML provider, has a bunch
of other services.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-04-01 19:18:12 | Re: View definition formatting |
Previous Message | Peter Eisentraut | 2003-04-01 18:30:55 | Re: View definition formatting |