| Re: Loop through array, change headings [message #184446 is a reply to message #184443] |
Wed, 01 January 2014 03:26   |
Denis McMahon
Messages: 634
Registered: September 2010
Karma:
|
Senior Member |
|
|
On Tue, 31 Dec 2013 21:08:20 -0500, richard wrote:
> Suppose I had a table that had 12 columns and 365 rows.
> Which would represent a calendar.
That's not how you'd represent a calendar in a database. You'd represent
a calendar as:
start time, end time (or duration), event id
In the events table, you'd have more info about the event keyed by the
event id, which might in turn link to other tables like contacts (for
people attending the event) by way of link tables (contact id, event id)
and locations (keyed by location id) for where the events are held.
The whole idea of relational databases is that the key information about
each contact, event or location is only held in one table in one place,
so eg if a contact happens to be an event attendee but also a location
manager, the same contact id is used in the attendee link table and in
the location table. Then if the contact changes their phone number,
instead of having to change that phone number in the attendee list for
every event the contact is attending and in the location table as the
location manager, you only need to change it in the contact table, one
change.
Not sure why I'm bothering to explain this. You seem to be genetically
incapable of absorbing and comprehending database theory.
There's all these people designing working databases all over the planet
using standard database theory, not to mention all the professors and
undergrads and PhDs etc that study, develop and teach those theories, and
then there's the richard methodology which seems to completely disagree
with what everyone else is doing and teaching and researching.
And richard continues to insist that he is right and the rest of the
world is wrong.
--
Denis McMahon, denismfmcmahon(at)gmail(dot)com
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]