>
> How different are special events from events? Can't you just have one
> Events table that holds them both?
>
> I would probably use:
>
> tblevents:
> intEventsID int(11) unsigned auto_increment
> intEventDatesID int(11)
> dtStartTime time
> dtEndTime time
> intEntLocID int(11)
> intEntTypeID int(11)
> intEntID int(11)
> dtUpdated timestamp
>
> tblspevents:
> intSpEventsID int(11) unsigned PRIMARY KEY
> txtSpEventsTitle varchar(255)
> txtSpEventsDesc text
>
> Just OUTER JOIN intEventsID in the second table to the first one and
> you have both in one table.
>
This may help to a degree, though I might then be applying a null value
to many of the fields in the events table, but theses fields are small
so it might not be too bad.
>
> Isn't this overnormalizing it a bit?
>
I don't think so. There may be as many as 15 or more event + spevent
records for any specific date. We may have 5 - 7 bands + 4 - 6 DJs + a
special event on any given day in the summer (depending on the
situation), only two of which (a dj and a band) will be in the same
location during the same time block.
>
> Are bands, dj's and other's really that different that they can't
> exist in the same table?
>
Bands are listed in the db with name, image, logo, website, type of
band, and if they are an active record. Djs are a name, image and if
they are an active record. Other can be almost anything and is mostly a
descriptive block (such as the concert tomorrow night). It can get very
complicated.
Cutter
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
