Originally Posted by dickersonka

When you say there is a relationship between the admin and the other entities, what do you mean?

They are allowed to edit as far as UPDATES, INSERTS, and DELETES or do you mean the admins are the owners of the movie hall? And just to be sure, hall means movie hall?

i would say to do it like this

admin -> hall -> branch -> movie -> seat -> customer

Originally Posted by timothybard

If the admin is just a list of people who can add, modify and delete records and is used only for database security/management purposes, then the admin entity would not have a relationship to the other entities in the diagram.

However, if you want to track, say, the admin who made the most recent change to a record in a database, then you could add an AdminID foreign key to each entity.

Lastly, as mentioned by dickersonka, if the admin actually owes or is responsible for a particular Hall, then you would have admin related directly to Hall.

I guess my real question is, are admins used simply to administer the database or are admins responsible for individual halls, branches, movies, etc. ?

and as i said before....the admin is just the database adminstrator and there is no individual admin.

My question is here...should i create a single relationship which is edit or update and link all the related entities together???

or draw multiple relationships that have the same action which is edit or update between the admin entity and the other entities??

Originally Posted by dickersonka

hmmm, still not perfectly clear to me, maybe tim understands a little more

are you meaning admin is a database user(windows / sql user account) or there is a table you are wanting called admin that has user credentials for an administrator?

Originally Posted by timothybard

I not sure what you mean by this:



However, let me make a few comments and see if they help:

For databases I've used in the past, there is a text field in each of the tables called "Updated By". Each time a record is updated, the field is updated to show the name of the person who made the update.

I've also used databases that makes copies of all updated records in a separate table so you can see the history of all the updates that have been made.

Lastly, you can't control who can make updates to a database simply by adding an admin entity to the database and adding relationships; you will need to program the database to lookup the current user and see if they are in the admin table; if they are not, the database must be programmed to not allow the user to make the changes.

Originally Posted by BeEasy

my question is in the ERD.....can i make more than three connection to one relationship.??