On Wed, May 21, 2025 at 2:22 PM Jim Jones wrote:
> In v10 I added this to the documentation to make the difference to CAST
> clearer:
Yes, that looks very helpful.
> In v10 I changed these comments to:
That, too.
I don't have time to re-review this right now, but I encourage you to
look throug
Hi Robert
On 21.05.25 19:10, Robert Haas wrote:
> Yeah. Just to be clear, I can't really think of committing a patch in
> this area because I don't know the topic well enough. I can make some
> general comments on what I see as issues with this patch but serious
> review would really need to come
On Mon, May 19, 2025 at 7:11 PM Jim Jones wrote:
> Not quite yet -- unless there is an expiration date that I am not aware
> of :). If we decide we don't need XMLCast on Postgres after all, I'd
> suggest to delete it from the todo list on the wiki [1] - I've already
> added a link to this thread t
On Mon, May 19, 2025 at 9:23 AM Jim Jones wrote:
> rebase
Hi,
Well, this patch is now more than 10 months old, and it's still the
case that nobody other than the author has said that they want this.
Is it time to give up?
I still don't think it's very clear either from the patch or from the
thr
rebase.
v5 also attached removes the libxml2 dependency of unescape_xml().
Background: the existing function escape_xml() intentionally avoids
libxml2 dependency and the previously used libxml2 functions
xmlStringDecodeEntities() and xmlDecodeEntities() got deprecated.
--
Jim
From f38c714220be8
On 12.11.24 15:59, Robert Haas wrote:
> Those are good things to check, but we also need to consider how it
> interacts with features PostgreSQL itself already has.
I totally agree. It just didn't occur to me to check how XMLTABLE()
deals with these conversions :)
> In particular,
> I'm conce
Hi Jim,
On Mon, Nov 11, 2024 at 2:43 PM Jim Jones wrote:
> > The only thing I found during a quick perusal of the documentation was
> > XMLTABLE(), which seems a bit baroque if you just want to convert one
> > value. Is this intended to plug that gap? Is there any other current
> > way of doing i
Hi Robert
Thanks for taking a look at it.
On 11.11.24 19:15, Robert Haas wrote:
> Hmm, this patch has gotten no responses for 4 months. That's kind of
> unfortunate. Sadly, there's not a whole lot that I can do to better
> the situation, because I know very little either about XML-related
> standa
On Sun, Nov 10, 2024 at 1:14 PM Jim Jones wrote:
> rebase.
Hmm, this patch has gotten no responses for 4 months. That's kind of
unfortunate. Sadly, there's not a whole lot that I can do to better
the situation, because I know very little either about XML-related
standards or about how people make
rebase.
--
Jim
From a43036de62a69c00d0c5c4469af02c8ded438530 Mon Sep 17 00:00:00 2001
From: Jim Jones
Date: Sun, 10 Nov 2024 16:13:18 +0100
Subject: [PATCH v4] Add XMLCast function (SQL/XML X025)
This function implements the SQL/XML function xmlcast, which
enables conversions between SQL data t
On 05.07.24 16:18, Jim Jones wrote:
> On 02.07.24 18:02, Jim Jones wrote:
>> It basically does the following:
>>
>> * When casting an XML value to a SQL data type, XML values containing
>> XSD literals will be converted to their equivalent SQL data type.
>> * When casting from a SQL data type to
On 02.07.24 18:02, Jim Jones wrote:
> It basically does the following:
>
> * When casting an XML value to a SQL data type, XML values containing
> XSD literals will be converted to their equivalent SQL data type.
> * When casting from a SQL data type to XML, the cast operand will be
> translated t
12 matches
Mail list logo
