Eric,
There are, as you will find out, a number of ways you could handle it. The
right way is really your decision and it's directly related to the
flexibility, maintainability, and security your site will require.
I have had success in the past using a role-based permission system. For
example,
Eric,
Your second approach is fine. It's denormalized, extensible, and can be
manipulated using tools you put in place.
You may want to consider groups as well, thus people belonging to a group
could view/edit pages, that has the potential to save a lot of
administrative scut work.
A table
At 23:36 01-11-2004, Eric Cranley wrote:
I tried to find this in the archives. If I missed it, my apologies in
advance.
I'm developing an intranet for my company, and we are planning on putting
sensitive information on it. I've already setup a login system using
sessions, but I'm not sure how to
i would add a second table and also store the totals
in the lyrics table like you suggested
then you can do things like top 10 this week / top 10
this month and make sure its not being abused
LYRICS_RATINGS - id | lyric_id | rating | vote_date |
remote_addr
same idea for hits/impressions
Yes, songs do span shows. However, the list of songs for each weeks
show starts out as a *.asc (same a *.txt) space-separated file. This
gets uploaded via a PHP file that formats each row and inserts it into
the database. That's why even though I know there will be duplication
it appears (to
From: Jason Lange [EMAIL PROTECTED]
Here's my question. I'm creating a website for a weekly radio show. One
of the items I would like to store in the database is the list of songs
played in each show (there's normally between 20-25 songs per show), and
the songs will be displayed by show.
Shaun,
I took a quick look at your database layout and noticed that Practice_ID and
Clinical_Trial_ID are repeated in the Booking table. This isn't necessary
because the Booking table links to the Project table which contains this
information. In the Project table, Practice_ID and
