On Friday, March 14, 2014 6:57:40 PM UTC-5, ONeal Freeman wrote: > > > > On Friday, March 14, 2014 2:12:17 PM UTC-5, RjOllos wrote: >> >> On Friday, March 14, 2014 8:24:10 AM UTC-7, ONeal Freeman wrote: >>> >>> >>> >>> On Thursday, March 13, 2014 6:16:53 PM UTC-5, RjOllos wrote: >>>> >>>> >>>> >>>> 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. >>>> >>> >>> Use trac-admin hotcopy to backup from trac 0.10.4 on linux server with >>> python 2.5 and sqlite 2.8.17 >>> >>> I do a straight windows drag and drop over-writing the default >>> environment created by the BitNami install; trac 1.0.1 using python 2.7.5 >>> and sqlite 3.7.6.2 >>> >> >> Would it be possible to either?: >> * Send the trac.db file for Trac 0.10.4 (if no proprietary data is in >> the database) >> * If trac.db contains data you don't want to release, create a new Trac >> environment on 0.10.4 with some dummy data that demonstrates the upgrade >> issue, and send over an archive of the environment. >> >> Is there a size limit I can upload? The db is 38MB > >
Because of time constraints and the need to get the new instance online, I used SQLite Administrator by Orbmu2k to export the table data from those 0.10.4 tables with time/timechange fields into a csv and then using the same application to import into the new 1.0.1 tables. I had to do it twice since the first time I exported data with a comma as the delimiter which caused data import issues. Second export I used a pipe as the delimiter. -- 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.
