This content has been marked as final. Show 2 replies
At first I was thinking of one table in the database for personnel. And the one table fore each person containing the movies and data for the movies
The question id then if it maybe is enough with two tables? One for persons and one fore movies that is linked with a "foreign key" in movies that keeps track on who have what movies
you´re on the right track with this approach -- one "movies" table would be all you ever need, as long you´d store the respective "personnel_id" in an extra column and define this one as foreign key to your "personnel" table´s primary key.
20 different jean_paul.php and filmjeanpaul.php?id=2
while it´s certainly OK to provide one "personnel_name.php" for each movie owner, I´d personally never link to individual "filmpersonnel_name.php" files from here, but rather provide one abstract "movie_details.php" page which receives the "personnel_id" as URL parameter, e.g. movie_details.php.php?personnel_id=4
I also want it to be easy to administer fore someone else but me. Eg delete and add persons and movies
you could use ADDT´s "levels" system for that, e.g. give an administrator a level of 1 and apply a "Restrict Access to Page" to the "admin_movies" lists and forms to make sure that only a "level 1" user can access these pages
Adobe Community Expert, Dreamweaver
Thanks for the input. I have now a fully functional site. (at another location than my testsite).
I have one more question before its complete. I'll post that in a separate post.