Re: help modeling a schedule system
| От | Scott Ribe |
|---|---|
| Тема | Re: help modeling a schedule system |
| Дата | |
| Msg-id | 363AF467-AD9B-4D2D-89C9-5594A0A1DBEA@killerbytes.com обсуждение исходный текст |
| Ответ на | help modeling a schedule system (chris h <chris404@gmail.com>) |
| Список | pgsql-general |
Well, when I did something similar a very long time ago, I put a "next time to fire" column in the table. Each time an eventis fired, the application updates that column. Was a lot simpler than baroque searches for events that would need firing between the last check and now. Was a lot cleanerthan creating tons of instances out through the future. You could create a stored procedure, if you want, to calculate the next time based on all the possible criteria. You could, have a "last time fired" column that keeps track of when the event was most recently fired, for logging/debugging/info.You could have a trigger that updates that "next time to fire" column each time the "last time fired"column is updated. -- Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice
В списке pgsql-general по дате отправления: