Posted by P Pulkkinen on 01/23/07 09:29

Check first, if they are open source apps available.

Depending on the generalization level I want to achieve, I would maybe start
with creating 3 database tables:

- events
- persons
- invitations (or events_persons, if you wish. it could imho handle both
invitations and replies to them)

But it really depends, how flexible system needs to be done. If there is
one invitator, there is no need for admins-table. If events are fixed, they
can be upated with phpmyadmin well enough. Also, are there two hierarchy
levels events like 1)different kinds of conferences that has 2) different
kinds of dinners.

I would also carefully think, could invited couples be handled in database
as one entry/couple. Since making those connections could be timetaking. But
this depends also, can those invitees split to separate dinners. For
example, some conferences have other events for men and other for women. And
then also, who of the two is "default" invitee, like one's son is default
guest for christmas table, but his new girlfriend is not supposed to come
ALONE, only with the son.

INVITEES
inv_id
inv_line (like Mrs & Mr Jones)
inv_min_seats
inv_max_seats

EVENTS
ev_id
ev_name
ev_date
ev_starttime
ev_endtime
ev_description

INVITEES_EVENTS
ev_id
inv_id
persons_coming
table_id
hotel_name
note_from_invitee

Making this a complete app would take some time.

DISCLAIMER: I wrote this all from purely altruistic point of view, I might
be wrong or right or in-between. I don't hold myself responsible of any
consequences that occur from using these ideas.

[Back to original message]