update from 1.8 to 1.x

Topics: Administration
Dec 24, 2014 at 9:24 AM
1.How to do?
  1. On 1.8 version there is some slow sqls( 262 records, 7600 ms, projector sql), is it still on version 1.x?
Developer
Dec 25, 2014 at 8:25 PM
  1. See: http://orcharddojo.net/orchard-resources/Library/DevelopmentGuidelines/UpdatingOrchard
  2. Impossible to tell without knowing those queries, but probably yes. AFAI remember there weren't ground-breaking performance improvements (though there were).
Dec 26, 2014 at 11:16 AM
Piedone wrote:
  1. See: http://orcharddojo.net/orchard-resources/Library/DevelopmentGuidelines/UpdatingOrchard
  2. Impossible to tell without knowing those queries, but probably yes. AFAI remember there weren't ground-breaking performance improvements (though there were).
Hello Piedone. I'm using and regularly updating my 1.x site already, but I have a question about migrations. How is the versioning handled in case there are modifications to these files? Is the upgrade version bumped up every time edit is made or there can actually be edits into existing versions? Because if someone fixes a mistake in them or adds features using same version I've merged in earlier the new code won't get executed and things can get messy. Should I watch out for such a scenario?

Thanks.
Developer
Dec 26, 2014 at 11:45 AM
That's a good point about migrations: if I understood correctly you ask what to do when there is a new migration step in one of the migration classes added, since your concern is whether existing migration steps (i.e. UpgradeFromX methods) just get updated in pre-release sources or new migration steps get added.

Generally the practice is the latter one: when somebody developers edit a migrations class, they always add a new migration step, regardless of that code not being released yet. There might by exceptions but AFAIK you don't have to be concerned about migrations. It's a different case with feature branches: those branches may evolve rapidly and are never meant for production use; but in 1.x or 1.8.x you can generally count on migrations being extended instead of modified.