Thanks for the replies, guys.
I need the schema enforcement up the hierarchy from what is being inserted to enforce uniqueness constraints (customer orders) as well as referential integrity (references to workcenters, suppliers, customers, etc.). Pulling the entire document and then validating would essentially be pulling the entire database--which would be ever-growing and won't scale. Schema-on-read is not sufficient for this application (the data in the database must be valid as it is used in realtime contexts), so I believe I will have to store the data in a relational database instead. :( I can imagine there would be difficulties in implementing such a thing in the database, so I am not complaining. :)
Regards, Paul Mensonides
----- Original Message -----
From: "Dirk Kirsten" dk@basex.org To: basex-talk@mailman.uni-konstanz.de Sent: Friday, February 20, 2015 3:15:52 AM Subject: [basex-talk] Fwd: Re: schema validation
After Christians mail I realized I pressed the wrong reply button, so I sent I forward my response to the mailing list.
But good to see Christian says basically the same :)
Cheers, Dirk
-------- Forwarded Message -------- Subject: Re: [basex-talk] schema validation Date: Fri, 20 Feb 2015 11:06:53 +0100 From: Dirk Kirsten dk@basex.org To: pmenso57@comcast.net
Hi Paul,
no, not directly. You would have to update via your own update functions by using our validation module. You could invoke all updates through such functions, e.g. by using RESTXQ.
BaseX itself is not schema-aware.
Cheers, Dirk
On 02/20/2015 03:33 AM, pmenso57@comcast.net wrote:
Hi all.
Is it possible to enforce schema validation on update in BaseX?
Regards, Paul Mensonides