Bob Gobeille wrote: > > On Feb 5, 2009, at 10:08 AM, Donohoe, Mark wrote: >> >> email_notification table: >> ------------------------- >> relation of email table to job table is many to one. Many e-mail >> tables to one job table. >> >> em_pk (primary key for the email notification table) >> job_fk (job table key) >> email_sent (timestamp or null) >> user_fk (user foreign key, email sent on this users request) >> email_addresses (comma seperated list of addresses used to send the >> mail) > > Do we really want to have an audit trail of email sent (the > email_notification table)? What's wrong with having a list of email > addresses in the users table. After a job, the notification agent > emails this list, which would be null if no notification is desired. > > Bob Bob,
You suggested the table. Here is the issue. I was going to add a column to indicate when the mail was sent. The problem with that is that if the user has 5 analysis jobs going, only the last one will be recorded. So above, I see you counter proposing that we keep no records of when a message was sent. The user supplies a list of addresses and we send it to them. That's it, dead simple. We don't record when we send a message. I'm fine with this design then. Make things a lot simpler to implement. Do you agree? -- Mark Donohoe ALPS/OSTT, Cupertino CA. fossology.org _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
