Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
Christian, your tip works great $ rb-site manage /var/www/reviews.example.info shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() quit() $ rb-site upgrade /var/www/reviews.onesys.info [...] -- begin log output -- Creating tables ... There are unapplied evolutions for accounts. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) *Evolution successful*. --- end log output --- And I said to myself : « what a wonderful world ! Thanks for your help Chris Le mardi 22 janvier 2013 23:30:39 UTC+1, Christian Hammond a écrit :Hi, Sorry to hear you got bit by some failed upgrade problem. All upgrades *should* be done in one transaction. It's *possible* that this is really a problem of some upgrade metadata that is screwed up. Something to try is: $ rb-site manage /path/to/site shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() Back up the database first, though. Once you run that, try to do an upgrade again. Christian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
Christian, your tip works great $ rb-site manage /var/www/reviews.example.info shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() quit() $ rb-site upgrade /var/www/reviews. http://reviews.onesys.infohttp://reviews.onesys.info example http://reviews.example.info.info [...] -- begin log output -- Creating tables ... There are unapplied evolutions for accounts. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) *Evolution successful*. --- end log output --- And I said to myself : « what a wonderful world ! Thanks for your help Chris Le mardi 22 janvier 2013 23:30:39 UTC+1, Christian Hammond a écrit :Hi, Sorry to hear you got bit by some failed upgrade problem. All upgrades *should* be done in one transaction. It's *possible* that this is really a problem of some upgrade metadata that is screwed up. Something to try is: $ rb-site manage /path/to/site shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() Back up the database first, though. Once you run that, try to do an upgrade again. Christian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
Thanks again for the prompt reply. If IE-7 is dropped and IE-X will not be supported going forward, I will pass it on and ask to use FF or other modern browsers. I was wondering whether I missed anything during the upgrade, thanks again. On Wednesday, January 23, 2013 3:51:09 PM UTC-6, Christian Hammond wrote: I'll see about spending a little it of time on it when I've solved a couple other bugs on my plate, but IE7 is one of the versions we've dropped, due to how difficult it is to get it to render correctly, and its lack of support for standards we're going to be making more use of. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Jan 23, 2013, at 1:49 PM, chella moneycome chell...@gmail.comjavascript: wrote: Thanks for the prompt reply, using IE 7. On Wed, Jan 23, 2013 at 3:28 PM, Christian Hammond chi...@chipx86.comjavascript: wrote: There's a fix coming for the console error bug in IE. (Good ol IE… only browser that gets this wrong.). What versions of IE are you using there? We're *strongly* encouraging modern browsers (not IE) from here on out, and will be aggressively dropping support for older versions of IE going forward. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
There's a fix coming for the console error bug in IE. (Good ol IE… only browser that gets this wrong.). What versions of IE are you using there? We're *strongly* encouraging modern browsers (not IE) from here on out, and will be aggressively dropping support for older versions of IE going forward. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Jan 23, 2013, at 1:24 PM, iamagui chella5...@gmail.com wrote: The actual site is live. I took a copy of the VM and trying the upgrade of 1.6.3 to 1.7.2. The upgrade was successful but the page(s) look different on Internet Explorer (IE) and FireFox (FF). Please refer attachments. The attached 'done-Error-IE.PNG' is the pop-up when I click the 'Done, but with errors on page' in the IE 'Status Bar'. Could you please let me know whether I missed anything during the upgrade. Kindly let me know if you want me to post this under a new topic. Thanks in advance. On Tuesday, January 22, 2013 4:30:39 PM UTC-6, Christian Hammond wrote: Hi, Sorry to hear you got bit by some failed upgrade problem. All upgrades *should* be done in one transaction. It's *possible* that this is really a problem of some upgrade metadata that is screwed up. Something to try is: $ rb-site manage /path/to/site shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() Back up the database first, though. Once you run that, try to do an upgrade again. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Jan 22, 2013, at 1:50 PM, christop...@gmail.com wrote: After some investigation, the reported error above was easily fixed. As it is clearly explained here, on Windows the default configuration of MySql doesn't allow default value for BLOB type. Setting sql_mode to MYSQL40 in my.ini solves the problem. But an error can hide another, and at the next run rb-site complained about a field diff_base64 which couldn't be added because it was present already. I guess that the origin of the problem is a previous unsuccessful upgrade attempt to reviewboard 1.7. Some database changes shouldn't have been reverted properly. This database schema problem could be very difficult to fix, I think I'm better off setting up a new reviewboard site from scratch. And from now backing up my database before every upgrade ! -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en login-IE.PNGlogin-FF.PNGlogged-in-IE.PNGlogged-in-FF.PNGdone-Error-IE.PNG -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
Thanks for the prompt reply, using IE 7. On Wed, Jan 23, 2013 at 3:28 PM, Christian Hammond chip...@chipx86.comwrote: There's a fix coming for the console error bug in IE. (Good ol IE… only browser that gets this wrong.). What versions of IE are you using there? We're *strongly* encouraging modern browsers (not IE) from here on out, and will be aggressively dropping support for older versions of IE going forward. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
I'll see about spending a little it of time on it when I've solved a couple other bugs on my plate, but IE7 is one of the versions we've dropped, due to how difficult it is to get it to render correctly, and its lack of support for standards we're going to be making more use of. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Jan 23, 2013, at 1:49 PM, chella moneycome chella5...@gmail.com wrote: Thanks for the prompt reply, using IE 7. On Wed, Jan 23, 2013 at 3:28 PM, Christian Hammond chip...@chipx86.com wrote: There's a fix coming for the console error bug in IE. (Good ol IE… only browser that gets this wrong.). What versions of IE are you using there? We're *strongly* encouraging modern browsers (not IE) from here on out, and will be aggressively dropping support for older versions of IE going forward. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
After some investigation, the reported error above was easily fixed. As it is clearly explained herehttp://stackoverflow.com/questions/3466872/why-cant-a-text-column-have-a-default-value-in-mysql, on Windows the default configuration of MySql doesn't allow default value for BLOB type. Setting sql_mode to MYSQL40 in my.ini solves the problem. But an error can hide another, and at the next run rb-site complained about a field diff_base64 which couldn't be added because it was present already. I guess that the origin of the problem is a previous unsuccessful upgrade attempt to reviewboard 1.7. Some database changes shouldn't have been reverted properly. This database schema problem could be very difficult to fix, I think I'm better off setting up a new reviewboard site from scratch. And from now backing up my database before every upgrade ! -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Django Evolution Error when upgrading database from 1.6.13 to 1.7.2
Hi, Sorry to hear you got bit by some failed upgrade problem. All upgrades *should* be done in one transaction. It's *possible* that this is really a problem of some upgrade metadata that is screwed up. Something to try is: $ rb-site manage /path/to/site shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() Back up the database first, though. Once you run that, try to do an upgrade again. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Jan 22, 2013, at 1:50 PM, christophe.one...@gmail.com wrote: After some investigation, the reported error above was easily fixed. As it is clearly explained here, on Windows the default configuration of MySql doesn't allow default value for BLOB type. Setting sql_mode to MYSQL40 in my.ini solves the problem. But an error can hide another, and at the next run rb-site complained about a field diff_base64 which couldn't be added because it was present already. I guess that the origin of the problem is a previous unsuccessful upgrade attempt to reviewboard 1.7. Some database changes shouldn't have been reverted properly. This database schema problem could be very difficult to fix, I think I'm better off setting up a new reviewboard site from scratch. And from now backing up my database before every upgrade ! -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
