[thelist] Doing things just once -- tracking in database.

[Fred Jones]

> I'm leaning toward an event table with columns "account_id",
> "event_id", and "processed_time" so that for any event I can find
> accounts that may be ready for the event (e.g. find all accounts
> that will expire in less than 10 days and do not have a row in the
> event table for the event within, say, the last 30 days).
>
> Does this seem like a sane approach?  Obviously, this is a common
> task for applications so I'm wondering if there are better solutions.

Sounds good to me. I have used a similar structure in projects.

HTH