Re: Review Board Ticket #4056: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2017-01-12 Thread David Trowbridge
-- To reply, visit https://hellosplat.com/s/beanbag/tickets/4056/ -- New update by Jasper For Beanbag, Inc. > Review Board > Ticket #4056

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-21 Thread Jasper Chow
Hi Christian I don't seems to be able to tell evolution recognizing my schema change. Can you please advise what is missing? [Basic Info] I have 1.7.0 installed with certain extra fields already in place For instance in accounts/evolution __init__.pyis customized with adding line

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-18 Thread Jasper Chow
Thanks for the detailed explanation Christian . I have a clear picture now. really appreciated. Don't think it is a good idea to ignore the rules applied to schema and just -execute all the way in every release. As eventually I will run into much bigger problem in the future. I revisited the

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-16 Thread Christian Hammond
Hi Jasper, --execute is fine, and it's what rb-site runs. It's the combination of that and --hint that gets you into trouble. I'll explain what's going on. Since we need to make changes to the schema for the database every so often, and since we support a variety of databases, we need to use a

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-15 Thread Christian Hammond
Hi Jasper, This definitely looks to be due to custom model changes made by someone there. You'll need to do some special stuff to disentangle these. You definitely don't want to use --hint --execute is a recipe for disaster (got a backup?). What you're going to have to do is take those old model

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-15 Thread Jasper Chow
Thanks for the feedback Christian I actually managed to get further by even smaller increments. 1.7.1 -> 1.7.2 ->1.7.28 and finally 2.0 The process is slow and i have to resolve things like Djblet needs to be updated, importlib missing etc so it seems to be working so far - why is

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-13 Thread Jasper Chow
Update: tried rb-site manage /path/to/site evolve -- --hint --execute but ends with Duplicate column error (password , or permission) hmm. further research it may not be due to our customization , but another case that the database somehow is in a bad state. I recall reading from some posts

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-13 Thread Jasper Chow
Attach evolve log ( rb-site manage /var/www/reviewboard evolve -- --hint ) for diagnosis thanks On Tuesday, January 12, 2016 at 12:58:01 PM UTC-5, Jasper Chow wrote: > > Hello > > I am having issue similar to previous reported, while running rb-site > upgrade > >

rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

2016-01-12 Thread Jasper Chow
Hello I am having issue similar to previous reported, while running rb-site upgrade https://hellosplat.com/s/beanbag/tickets/3967/ https://www.mail-archive.com/reviewboard@googlegroups.com/msg15947.html information: on Linux (CentOS) reviewboard 1.7 -> 2.0.16 ( intended to upgrade to latest

Re: Site-upgrade error

2012-04-17 Thread Viktor Jozsa
We use MySQL database, but we use formerly database is SQLite in test phase. At 2011. August install the new server and import data to MySQL by hand. We're creating backup every night. Viktor On ápr. 16, 20:17, Christian Hammond chip...@gmail.com wrote: That looks like some data corruption in

Re: Site-upgrade error

2012-04-16 Thread Christian Hammond
That looks like some data corruption in your database. The serialized data describing your database schema is either corrupted or can't fully be read. What database are you using? Do you have a backup? Christian On Apr 16, 2012, at 3:57, Viktor Jozsa jozsa.vikt...@gmail.com wrote: Hi!