> Ok, progress and headway is being made, but now I'm a little stuck.
> I've created three tables, one for events (tblevents), one for
> holiday or "plus" events, and a table for special events
> (tblspevents).
How different are special events from events? Can't you just have one
Events table that holds them both?
> 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 auto_increment
> intEventDatesID int(11)
> dtStartTime time
> dtEndTime time
> txtSpEventsTitle varchar(255)
> txtSpEventsDesc text
> dtUpdated timestamp
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.
> As you might see, the top two tables (tblevents and tblspevents) are
> tied to another table (tbleventdates) by that tables pk
> (intEventDatesID). Here is its general layout:
>
> tbleventdates:
> intEventDatesID int(11) unsigned auto_increment
> dtDates date
> blSpEvent tinyint(3)
Isn't this overnormalizing it a bit?
> 1. pull all records from the events table (tblevents) with a
> specific date (or the next date with an event) [easy by itself] and
> then pull the proper entertainment (intEntID) from the proper table
> (tblbands, tbldjs, or tblother) depending on the type ID. And sort
> it by location and start time [***HELP***]
Are bands, dj's and other's really that different that they can't
exist in the same table?
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
