Re: bug hunting idea

At 03:32 PM 8/4/00 -0500, you wrote:

Suggestions from my experience: Let people set their own frequency. It's not hard to store another integer denoting their frequency, and a datetime of when you last bugged them, in the row with their email, and then you can only bug them as often as they want to be bugged. Also let them turn it off for vacation or whatever.

Good points. I can set the bug system up with the defaults desired by the developers and qa team.

I also factored in that the Venue in question may have been contacted by the system automatically to update their own records, and we wanted to contact the venues whose data was least "fresh". This did make for a pretty gnarly query, but I was very inexperienced then (and still am not SQL expert) so maybe it's just bad code... If you think the PostgreSQL code that does this would be handy, I'd be happy to forward it to you... But be warned it has a lot of extra crap in it that will just get in your way, what with the venues being able to update their own data, and the idea of "freshness" stamping records.

Please do - I think that this should be simple.. however I have been wrong on at least two other occasions in my life :D If I do understand the functionality correctly, then this should be not be too bad to do. something like: SELECT ... FROM user WHERE last_notify < now() - notify_interval AND now() NOT BETWEEN vacation_start AND vacation_end Should do the trick... Zak