Isn't it basically an issue for optimizing for how you expect the
DBMS to be used? If you expect to process primarily queries and bulk
inserts, then it makes sense to allocate large blocks of storage than
if you expect a lot of updates of smaller records.
Oh, and I completely agree with you that VistA supports a relational
model of data access (even if it doesn't require it), and that it is
inaccurate to refer to it as "hierarchical". Someday, I'm going to
have to sit down with Codd's rules and see how Fileman fares.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"A practical man is a man who practices the errors of his
forefathers. -- Benjamin Disraeli
On Sep 19, 2005, at 12:49 PM, Cameron Schlehuber wrote:
Many "relational" databases do waste space, but since even M
databases can
project a SQL view (relation), that argument may not always be
accurate. In
my opinion it's misleading for folks to claim that VistA is
hierarchical and
therefore cannot project a relational view.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
