Difference between revisions of "DOM runtime database"
m (catg subsys)
|Line 27:||Line 27:|
[[Category:DOM |runtime database]]
Revision as of 01:24, 19 April 2007
The DOM runtime database is a resident, active cache of COLLADA elements. This cache is based on C++ COLLADA elements handed to the cache by the COLLADA DOM backend. It is sometimes referred to simply as the DOM database.
Using the database
The database is represented by the daeDatabase class, which is useful for manipulating documents and for retrieving elements after they have been loaded into the database or before saving them from the database. For more information, see:
The DOM database is straightforward except that it needs to be thought of as a runtime database, since a persistent database store (XML database, SQL database) would be implemented as an I/O plug-in.
Insertion and deletion
The database does "lazy" insertion and removal of elements. It keeps a list and then does the actual insertion or deletion upon the next database query, if any.
The queryElement function has never been implemented but would most likely be used to parse XPath or XQuery expressions. The current DOM cannot do full XQuery support because there is no way to address attributes or values by themselves and XQuery allows you to get lists of all attributes that … , etc.
The stlDatabase is the default implementation of a daeDatabase. Someone might want to write their own database if they want database paging, that is, moving data in and out of memory based on usage. (This would require a lot of work besides just writing the database, though.)
The database contains two structures to store all elements:
- A sorted list of all elements, sorted by element type.
- A multimap with the key being an element ID and the value being the elements themselves.
- The multimap is used to speed up URI resolution because URIs query the database by element ID. It is also used if the user supplies an ID for the getElement or getElementCount query functions.