kirk112 Posted October 15, 2007 Share Posted October 15, 2007 Hi I currently have the following table structure. jbe_messages jbe_message_id jbe_id candidate_ref message opened clicked date_sent jbe_settings jbe_id candidate_ref jbe_settings active date_created This structure stores all the search information in a serialized string in the jbe_settings field and the contents of the message in the jbe_messages->message. Which works fine, but I am trying to think of a way in which I can track all of the different jobs that have been sent to a specific candidate (tracked by job_id which is the primary key of the jobs table) so that each time the script runs it does no send the same job to the same candidate more than once. I have thought about having a extra table Jbe_sent_jobs Jbe_sent_id Jbe_message_id Job_id And each of the job_id that are sent are stored in this table, the problem with this is that this table would become very large very quickly i.e 5000 different emails, each with 40 jobs (200000 records from the first send out and the emails are normally sent twice per week). Can anyone think of a better way of storing this information. Thanks Quote Link to comment Share on other sites More sharing options...
fenway Posted October 15, 2007 Share Posted October 15, 2007 You'll not have much of a choice as far as storing e-mails... you could try and use bit flags, but that's ugly Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.