Michael,
>> it a huge
>> conceptual mistake to make document computing the centerpiece
>> of database design
MK> cases where it works well:
MK> (a) where the documents map well to the business objects that are the
MK> primary information content of the database.
What is the business objects ?
If documents are maping well (all items are predictable, repeated),
whether it's better to save under usual relational engine instead to save xml ?
MK> When these conditions don't hold, for example with an HR database ...
MK> document-centred modelling certainly has its limitations. ...
What limitations ?
And how is these limitations look in particular case of
file system as hierarchcal database and html-documents as document-centered modelling.
Dmitry Turin
HTML6 (6. 5.3) http://html60.euro.ru
SQL5 (5.11.1) http://sql50.euro.ru
Unicode7 (7. 2.1) http://unicode70.euro.ru
Computer2 (2. 0.2) http://computer20.euro.ru
