From: er0ck <er...@gm...> - 2011-11-12 17:21:39
|
date types can't store just month/day (they need a year for valid logical comparisons). day of year might be doable. could get messy in leap years if seasons begin/end at end of february. i define "seasons", for now as 3 months each (and a season called "all"). fall is sept-nov. winter is dec-feb (messy). for now i only allow 4 seasons, but i can see very quickly users wanting more granular seasons. do your items/produce get properties of "season" or properties of your recurring event (as defined by users)? in the latter case to use day of year we'd probably need a calculator/template so the user could enter gregorian dates and we'd figure out the day of the year. and it would still get messy in leap years. ______________________________________________ Too brief? Here's why: http://emailcharter.org On Fri, Nov 11, 2011 at 23:39, Leonard Wallentin <leo...@ho...> wrote: > Aha, I see. Do you really need to store the values like that, or could you > use the day of the year instead? Or date type valies? > |