On Thursday, March 13, 2014 1:26:59 PM UTC-7, hasienda wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 13.03.2014 21:00, ONeal Freeman wrote: > > I just determined that the trac-admin <path to env> upgrade is wiping > > out the time and timechange fields. > > Which db upgrade do you mean, a Trac core upgrade module? > > Steffen Hoffmann > > > PS: Despite of posting below the last message text it has been hard to > spot that comment to yourself in your latest message. Would you try to > do the e-mail message threading more obviously, please? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Icedove - http://www.enigmail.net/ > > iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 > vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu > =ptrw > -----END PGP SIGNATURE----- >
I would look at whether the other fields involved in the seconds -> microseconds timestamp conversion also exhibit the problem. The fields are shown here: http://trac.edgewall.org/browser/trunk/trac/upgrades/db25.py?marks=20-28&rev=12014 Knowing the exact steps you took, and the System Information (e.g. SQLite and Python versions) on both systems would also be helpful in helping us sort through the issue. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
