Re: [Trac] Re: Trac.db questions
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 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 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.
Re: [Trac] Re: Trac.db questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.2014 21:00, ONeal Freeman wrote: > I just determined that the trac-admin 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- -- 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.
Re: [Trac] Trac.db questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.2014 18:00, ONeal Freeman wrote: > I am migrating trac 0.10.4 from a linux server onto a new trac instance > 1.0.1 on windows server. > > I copied over the trac.db to keep our existing tickets. > > I have just noticed that the ticket.time, ticket.changetime, and > ticket_change.time fields are 0 in the copied db although those fields > are correct in the original backed up db. > > Has anyone else experienced this? No, although I've been moving several Trac environments, version 0.12 from GNU/Linux to Trac 1.1.1 on WinXP myself. > I am thinking that this was caused by the trac-admin upgrade command or > the installation of the TracTicketTemplatePlugin which apparently adds a > new table, ticket_template_store to the db. I know that each such Trac db upgrade leaves a copy of the old (SQLite) db in the /db/ directory, so you could easily confirm or rule that out yourself. Since the plugin in question does add a new db table but has no business like altering db table 'ticket' I cannot see a justification for such a suspicion. > Am I suppose to do a import of some sort to preserve my data? Always keep a full Trac environment copy before changing things. Apart from that Trac will tell you required steps. I've upgraded Trac environments a lot within the last 5 years and never encountered data loss like you suggest that it happened to you. I do not tell you, it is impossible, but highly unlikely, and certainly not normally to expect. There might be some non-obvious things that stepped in your way. Did you copy the db while the environment was active? You should at least us the trac-admin db hot-copy command and only move that offline copy of your db. You might want to move a tar or zip archive instead of the raw db to detect data alteration on archive unpacking time at the target system. These are just some thoughts from the top, without knowing details about your migration process. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMiE3YACgkQ31DJeiZFuHf1pgCgqUZ9rcON/ArmPI8Rpn3q7QMA a6oAnj3hpN3IC+MdTdIZTAsRwG4nPbD4 =L39w -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.
[Trac] Re: Trac.db questions
On Thursday, March 13, 2014 12:00:15 PM UTC-5, ONeal Freeman wrote: > > I am migrating trac 0.10.4 from a linux server onto a new trac instance > 1.0.1 on windows server. > > I copied over the trac.db to keep our existing tickets. > > I have just noticed that the ticket.time, ticket.changetime, and > ticket_change.time fields are 0 in the copied db although those fields are > correct in the original backed up db. > > Has anyone else experienced this? > > I am thinking that this was caused by the trac-admin upgrade command or > the installation of the TracTicketTemplatePlugin which apparently adds a > new table, ticket_template_store to the db. > > Am I suppose to do a import of some sort to preserve my data? > > Thanks in advance for assistance. > O'Neal > > I just determined that the trac-admin upgrade is wiping out > the time and timechange fields. > -- 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.
[Trac] Trac.db questions
I am migrating trac 0.10.4 from a linux server onto a new trac instance 1.0.1 on windows server. I copied over the trac.db to keep our existing tickets. I have just noticed that the ticket.time, ticket.changetime, and ticket_change.time fields are 0 in the copied db although those fields are correct in the original backed up db. Has anyone else experienced this? I am thinking that this was caused by the trac-admin upgrade command or the installation of the TracTicketTemplatePlugin which apparently adds a new table, ticket_template_store to the db. Am I suppose to do a import of some sort to preserve my data? Thanks in advance for assistance. O'Neal -- 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.
