public inbox for [email protected]
help / color / mirror / Atom feedFrom: Pavel Stehule <[email protected]>
To: Jim Jones <[email protected]>
Cc: Marcos Magueta <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: Kirill Reshke <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: WIP - xmlvalidate implementation from TODO list
Date: Wed, 1 Apr 2026 18:57:24 +0200
Message-ID: <CAFj8pRDEOmkafV3s7XjCK-DzvnhoxgvHWJ7tChUi=-8zJ20Vog@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAN3aFCdx8AapWSVpJ1kaC7OC_v7QwbjgbGw9WfPBBY2GMyOadQ@mail.gmail.com>
<CAN3aFCecpcPBs4x3KUuxTqvY2VzpCZZKrBphNaQjE5uD8UtEpQ@mail.gmail.com>
<CAN3aFCcb0Nvap1CKShd5RNa+V+pray+ur_LtOON3nkwqdh5NMA@mail.gmail.com>
<[email protected]>
<CAN3aFCdW3_RNgidcV_vWA-NFeYf6p7M5VMG8moSzk3bBJneUxQ@mail.gmail.com>
<[email protected]>
<CAN3aFCfkrkOJ+R39x=9qvXMGLE3yuL9fZdNyRa5V=BAdGGu=-g@mail.gmail.com>
<[email protected]>
<CAN3aFCcvXHmW+FKS7gX=HoUcjku2nr7XKJEZm05DrgsQxy79HQ@mail.gmail.com>
<[email protected]>
<CAFj8pRB3d_fREmgzT1GQwG_wfR1brxyTMVsAV=bbpOzvPkauLg@mail.gmail.com>
<[email protected]>
<CAFj8pRBg6bbO4YiSO633RHMOqQ3jAtVtCq=oN8TPE2FHG9LY2Q@mail.gmail.com>
<[email protected]>
<CAFj8pRBq4580f5n7DTe7x+SWqCS_d=e1Of7snUNaKk8_L1g28Q@mail.gmail.com>
<[email protected]>
st 1. 4. 2026 v 16:39 odesÃlatel Jim Jones <[email protected]>
napsal:
>
>
> On 01.04.26 10:10, Pavel Stehule wrote:
> > maybe it can be implemented just as an extension - we don't need DDL
> > commands CREATE XMLSCHEMA - there can be some function. If I understand
> > correctly, the SQL/XML knows just XMLVALIDATE command - and in the first
> > step - this can be just a function too.
>
> Yeah, the spec does not dictate how the schemas are stored or how
> identifiers are mapped to XSDs. The way I see it, in the current state
> of this patch, we miss the option to add XSDs to an existing XMLSCHEMA
> identifier (something like ALTER XMLSCHEMA .. ADD ...), or even the
> option to pass multiple XSDs in CREATE XMLSCHEMA.
>
> It makes the implementation of CREATE XMLSCHEMA (or similar DDL) a bit
> more challenging, as it must always resolve all root's dependencies to
> ensure that XMLVALIDATE has all the necessary info to validate a given XML.
>
> >
> > Theoretically there can be different access - we can introduce a generic
> > XMLVALIDATE command, that can call some callback. This callback can be
> > implemented in an extension. One extension can XML storage identified by
> > relation identifier, another can implement some shared storage on the
> > disc outside the database etc. So the organization of the patch can be
> > different
> >
> > 1. creating API for extensions for implementing loading the schema from
> > some sources.
> > 2. implementation XMLVALIDATE that uses this API
> > 3. creating an extension in contrib, that implements XML storage
> > identified by relational API.
> >
> > Because we don't have an extensible parser, the XMLVALIDATE command
> > should be in core, but other parts are not.
>
>
> How would XMLVALIDATE without this contrib extension look like?
>
The API can be similar to PLpgSQL plugin API - and rendezvous variable
Pavel
>
> Best, Jim
>
view thread (17+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: WIP - xmlvalidate implementation from TODO list
In-Reply-To: <CAFj8pRDEOmkafV3s7XjCK-DzvnhoxgvHWJ7tChUi=-8zJ20Vog@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox