[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XML Schema for large database
Title: RE: XML Schema for large database Bill, One thing to keep in mind is the structure of the schema (and therefore the corresponding XML documents), as this may affect locking when committing information to a database (and the more information you have, the longer the duration of the locks). That is, suppose you have an Order table and an Item table - there are 2 basic ways to structure this information: (1) "Nested" approach
In (1), the XML document would look as follows (as you can see, the Item records are "nested" inside their corresponding Order records): <Orders>
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. The more tables that are involved, the more simultaneous locks that need to be held. There are certainly creative ways around this, but these would involve an intermediate step that places the information in a more "lock-friendly" structure. In (1), the information is in "blocks" that correspond to database tables. For example: <Orders>
With this approach, only the Order table needs to be locked when committing Orders to the database, then only the Item table, etc. The only caveat is that there needs to be a cross-reference from Items to Orders, so that it is clear which items belong to what orders (see orderID attribute above). Hope this helps,
> **************************************************************************
-----Original Message-----
Wanting to serial the contents of portions of a large database, i.e. 500 -
Trying to understand the implications of creating a XML Schema that reflects
I would auto create the XML Schema from the database's metadata. But would there be problems with parsers or transformation engines being
I have been toying with the idea of breaking up the logical model into
Or have the minimal about of data in one xml file. and collect the files in
Is it possible/probable that a large schema would not be able to be
Bill Riegel
-----------------------------------------------------------------
The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|