While I currently have about a dozen tables, I'd like to throw this one up for any opinions, suggestion, warnings, things I may not be saying. It's not a started entity - schema diagram but should be clear for the purposes of the email.
"Table: Posts" (innodb) ------------------------------------------ PostID (auto inc, int) set to PK ------------------------------------------ Entered (timestamp) ------------------------------------------ StartP (timestamp) (user decision) ------------------------------------------ PLen (Int) (user decision) ------------------------------------------ VenID (int) (Not FK'd to the VenTable though, don't see the need) Session variables and joins keeping them related ------------------------------------------- Ind (varchar) based on user choice from menu provides IndID from static table ----------------------------------------- City - (varchar) based on user choice from menu provides CitID from static table ------------------------------------------- State - (varchar) based on user choice from menu provides StatID from static table --------------------------------------------- Term - (varchar) based on user choice from menu provides TermID from static table ------------------------------------------ Rate - (varchar) User text input ---------------------------------- Contact - (varchar) right now they are pulled dynamic fields from the Ven Table, defaulted into form for Posts and put into this table -------------------------------------------- Contact Email - (varchar) same as above - I'm starting to see an issue here, meaning, possible bad design), My strategy was that one company may have an account with various users sharing the one contact name and password. Not sure. -------------------------------------------- One more insignificant field. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
