Re: I think that relational DBs are dead. See link to my article inside

> I sincerely doubt there is anything you can do in a network model DB that cannot be done at least as well in a Relational model DB. Give just ONE example.
in a Relational model DB. Give just ONE example.

I am not sure if this would qualify, but I would like to see an equivalent RMDB implementation (and also how resilient it is to handling additional data that is unknown during initial db design) for the example posted at www.dbfordummies.com/example/ex012.asp

In general, this example could represent the following: There are 1 to many courthouses.
A courthouse has 1 to many floors.
A floor has 1 to many rooms.
Persons in the courthouse can have 1 to many classifications (ie judge, clerk, coordinator, bailiff, court reporter, assistant, etc).
A person can have 0 to many names, phone numbers and emails. A person can have 0 to many bosses/employees. The location of a person can be specified by a building, floor, room, etc.

More specifically, this example represents:

Judge Judy has the following employees:
clerk Clark, coordinator Colby, bailiff Brandy and court reporter Courtney.
Assistant clerk Ashley is an employee of Clark and Colby. Each person has various attributes some with multiple values.

Courthouse1 has two floors.
It's first floor has room1.
It's second floor has room1 and room2.
Above persons are located in different parts of Courthouse1.

The first figure displays Courthouse1's parts. The second figure displays attributes of various persons. The third figure displays inverted isIn/boss hierarchies with Ashley as the root.

There are a number of queries such as:
Find all persons.
What does Courthouse1 have?
Find Ashley's bosses.
Find a judge's employee whose employee phone# is 737-5588) Courthouse1's floor2's room2 has which person that has an employee names Clark and an employee whose email is colby_at_msn.com.

Additional details documented in script's comments. Received on Mon Jul 03 2006 - 22:27:03 CEST