Re: Nikon FDUtility



Don (phoney.email@xxxxxxxxx) wrote in
news:rj9pu1pvbookqc2p4n9bub0454psv3ut2h@xxxxxxx:

It is indeed comparable to database design. And a hierarchical
database is possibly the closest parallel (although with adding
symbolic links/shortcuts you end up with something more like a network
database). So why come up with the relational model? It does *not*
apply at all, it's a totally different organization.

No, it's not! A relational data base model is based on logical indices

Eh? Where did you get the idea that a relational database is based on
"logical indices"?

And have you even considered *how* a hierarchical database has
similarities with hierarchical directories? Have you ever *used* a
hierarchical database system? I suspect not.

Symlinks and shortcuts would be crutches in both models - that's just an
extra layer. But directories have direct links to their parents. That's
exactly what you have in a hierarchical database - there's no such
concept in a relational model (you can implement it in data - but that's
not the same thing at all).

Here we agree. It would, logically, be the best thing to do. Except
Windows would soon lose a lot of customers is MS actually did that ...
people, and applications, would no longer be able to find their data!

Oh, but they would, if implemented properly.

Applications, if re-written, would. Humans would not - and they can't be
rewritten. ;-)

--
Marjolein Katsma
*Help with HomeSite/Studio: http://hshelp.com/
*Travel blog: http://blog.iamback.com/
*Spam reporting addresses: http://banspam.javawoman.com/report3.html
.



Relevant Pages

  • Re: Databinding - Best Practice (object-oriented)
    ... > OO is for application development only, not for Database Systems ... Applications are only a part of an Information System. ... relational model throughout your application severely restricts the ...
    (microsoft.public.dotnet.framework.windowsforms.databinding)
  • Re: Databinding - Best Practice (object-oriented)
    ... > OO is for application development only, not for Database Systems ... Applications are only a part of an Information System. ... relational model throughout your application severely restricts the ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Data Layer architecture
    ... > the first week of>> any serious database course). ... rules were described to be inside the RDBMS, ... is not a theory which states anything about business ... > The Relational Model is nothing but a direct application of set theory ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: POD speed
    ... > appropriate when data spans applications. ... > Enforcement of database constraints in application code is one solution ... which would result in a relational model being more appropriate. ...
    (comp.lang.java.databases)
  • Re: WWW/Internet 2009: 2nd CFP until 21 September
    ... afterwards focussed on the application of the relational model to the ... organization of data banks for large scale sharing of data. ... by a single application inside which the database is to be embedded. ... lack of transaction control wasn't really the reason reservation systems ...
    (comp.databases.theory)