tudborg

9 ms·

1. 61.▲
   by tudborg 13y ago

   Simply use and store everything in UTC. If you ever need to do grouping by time in any other timezone, it would be trivial to do the conversion. DAYOFYEAR( CONVERT_TZ(my_datetime_field,'+00:00', '+02:00') ) Seems very in
2. 62.▲
   by tudborg 13y ago

   If you have an indexed DATE or DATETIME field in MySQL, you really want to use the date and time functions to do your grouping. This seems to add unnecessary complexity and overhead. There is already plenty of build-in abstraction for date
3. 63.▲
   by tudborg 13y ago

   All good fun. But in all seriousness, don't do this on your site. It is horrible.
4. 64.▲
   by tudborg 13y ago

   Not sure if you are joking?
5. 65.▲
   by tudborg 13y ago

   It very much depends on the application. What is the size and scope of the project? What feature-set are we looking at? Anything realtime? Performance critical? Large team building components at the same time? Maintainability? Scale? If you
6. 66.▲
   by tudborg 13y ago

   You need to go look up "prototype" ;)
7. 67.▲
   by tudborg 13y ago

   Or maybe the issue tracking system is a web tool that links to the file in the repository and you could fix it with a click to edit instead of pull,open file,fix,commit,push. Documentation or fixes to comments in code is an obvious usecase