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

RE: XML Schema for large database

• To: Jeff Lowery <jlowery@s...>, "'CHIUSANO, Joseph'" <JCHIUSANO@l...>, 'Bill Riegel' <BRiegel@l...>, "'xml-dev@l...'" <xml-dev@l...>
• Subject: RE: XML Schema for large database
• From: Jeff Lowery <jlowery@s...>
• Date: Thu, 15 Aug 2002 10:36:01 -0700

Sorry, that last message got garbled:

> -----Original Message-----
> From: CHIUSANO, Joseph [mailto:JCHIUSANO@l...]
> 
> 
> It seems reasonable to assume that when committing this 
> information to a
> database, one may have to lock multiple tables simultaneously (thereby
> violating the best practice rule of "hold locks for as little time as
> possible").  That is, the Order table would need to be 
> locked, then the Item
> table (while the Order table is locked), etc.   
 
 Why the assumption of table-level locking?  Neither do I see how the
 structure of the XML document matters, assuming you have a 
 database that
 supports optimistic concurrency and atomic transaction commitment.
  
 However, if you're using MS-Access in a multiuser 
 environment, there's no
 hope for you anyway. :-)  

• Prev by Date: Re: Re: Can XLink be fixed?
• Next by Date: Re: SLAIX (was: Can XLink be fixed)
• Previous by thread: RE: XML Schema for large database
• Next by thread: RE: XML Schema for large database
• Index(es):
  • Date
  • Thread