[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SV: When to Validate XML?

• To: xml-dev@l...
• Subject: Re: SV: When to Validate XML?
• From: Subrahmanyam Allamaraju <subbu@b...>
• Date: Tue, 06 Nov 2001 19:03:30 -0700
• References: <E6CDEF4DFA31524D83641C6B9550AF77D33DCF@e...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913

> 
> So you can use RDBMS triggers and rules to handle a lot of those checks
> that you otherwise would have to write in every application. Great. On
> the other hand, there are application specific rules, that cannot be
> implemented in the DB. (And yet, using e.g. Oracle and PL-SQL, you can
> create some very nifty rules and triggers...)
> 
> I also agree a lot with the other statements, about using triggers and
> rules in the DB is the only way to ensure integrety on the DB level,
> which is especially important in e.g. a n-tier architecture, where the
> DB is accessed from many different applications.


Good point. Hence the question - what does schemaless persistence mean 
(as offered by most XML-DB vendors) for such applications? The whole 
idea of schemaless persistence is based on extensibility, 
semi-structuredness, etc. How do these vendors react to the question of 
DB-level validation?

 
> Hmmm. Any read the book "Business Component Factory" by Pter Herzum and
> Oliver Sims? It touches some of these issues from a CBD viewpoint.


I've read this. Which specific issues are you referring to?

Subbu

• Follow-Ups:
  • RE: SV: When to Validate XML?
    • From: "Michael Kay" <michael.h.kay@n...>

• References:
  • SV: When to Validate XML?
    • From: "Jens Jakob Andersen, PDI" <jens.jakob.andersen@p...>

• Prev by Date: Re: Re: determining ID-ness in XML
• Next by Date: fyi - Building an XML-based message server
• Previous by thread: SV: When to Validate XML?
• Next by thread: RE: SV: When to Validate XML?
• Index(es):
  • Date
  • Thread