database setup - opinion needed

[danielle]

Here's a database set up question

i have 5 tables ...

admin/user (table with login info)

program_main
program_topics

program_main_temp
program_topics_temp

if a program is added or edited - a user gets added into the admin table and the program data goes into the temp tables until approved by the Site admin - when approved -the info goes into the live tables and can be viewed on the site.

i currently have the primary key of the program_main table running the whole show but would it make more sense to have the user's primary key in the Admin table holding all the data together?

as of right now:
in admin table we have [e-mail] id=10
joe gets his program data entered into the temp table:
i set "program_main_temp.add_user=10"
the ID of that row added is 7...

we then put the program topics into the topic_temp table:
set "program_topics_temp.program_temp_id=7"

admin Sally comes, approves the add -- all the info gets put into the program_main, program_topics table - we now have a program_id...

<<<that's all my current set up... i am leaning towards running it all off the admin id--what do you think..??

but! then again - i should probably keep the program info all together...

grrrr

[tomhath]

As long as it works I'd leave it alone.

But I'm not sure why you have the _temp tables. Why not just have a flag in the main tables that indicates whether the admin has approved it?

[danielle]

I'm still in the beginnings of development so changing isn't too big of an issue now...

And as far as the temp table... their profile will be live on the web and updates they make must be approved as well. The temp tables will store the un-approved version and when that's approved it will overwrite the main tables.

I'm having a hard time with it cause it's actually written in asp.net/c# but I slipped over here for the DB question because I always get good input here... it's my favorite forum.