-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19.03.2014 14:54, ONeal Freeman wrote: > I will admit that I am struggling with the queries trying to get tickets > close during a period like the last 30-days. I am quite confused as to > why the developers would chose to use seconds and milliseconds but who > am I...
As you've not been involved into related issues and development, this is a valid question. In short, we've got reports of issues with timestamps when doing automated changes within some milliseconds while the time resolution has been "only" seconds. I.e. it was no longer guaranteed, that composite keys in ticket_change db table consisting of timestamp + ticket ID were unique for each change. Accounting for future improvements of IT equipment and making a step into safe water it was consequent to boost time resolution by a factor of 6 - up to microseconds, you see? You'll make your way with adapting queries to that time stamps too. For issues browse the mailing list first, and ask detailed questions, if required. Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMp4GUACgkQ31DJeiZFuHcMOACcDAL6Odew9K/u5OA0c3E46e9r gsIAn3NBN5rADFIUsVvasPV3/Kam30qu =vkrY -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
