Hello Everyone,

I posted this accidentally in the "MySQL" forum before I saw this one, so sorry about that.

I am working on a web application that has users log in to their account and create 'events'.

There is a single table for all users, with a primary key of their email address.

I can see 2 ways for each user to be able to create accounts:

1. I could create another table with all posts and an auto_increment key. Then, I could create a relational table that has email address and the key from the events table.

2. I could create a different table for each user that contains all of their events.

Which way is more practical/faster? I'm brand new to this stuff. Thanks everyone!

-Greelmo

first thing you need to do is clarify whether you're talking about accounts, users, events, or posts

those are at least two, possibly three or four tables

but at no time would you assign a new events table to each user

Yes, sorry. I realize I didn't type that very clearly.

I have the accounts table already set up. I'm trying to design the system for each user to be able to post events.

What is the best way to do this?

one table for events

include a user FK column to relate each event to its user

How can you set up events tables to delete events that have past from this structure?

Do you have to do this manually? I'm using PHP and MySQL

as opposed to automatically?

use a cron job