boyter
Create upgrade script
At least let us know about structural changes, as new column in repo table was a surprise, especially that is seems that is has to be initialised with not null data (maybe default value on it could work).
Also if it would be not to problematic, it would be great to see links to work items in release note, so if someone needs more info about what happened, it would be easy to learn.
Cheers, J
Currently i have a script that checks if the version number has changed and if so it deletes the repos/index files and replaces the database with the one from the zip. Thats the only way i have been able to upgrade searchcode. Of course I still need to click "Reclaw and Rebuild Indexes" after all this is done.
this time I tried sqllite script to recreate my repo list and it was throwing errors allover the place due to missing column.
Sorry about that. I didn't catch that I added a new column in my pre-release tests (single man shop here!). Links in the release sounds like a good thing to do. Moving forward I will do so.
@bskrtich Thats the recommended approach really. It makes it easier from an upgrade perspective and one reason why I added the API so that it could be done. You shouldn't need to click "Recrawl and Reindex" though unless you are doing a hot swap, restarting the application should effectively do this for you.
@quasarea Looking into that issue now.
Thinking that for the future that the best way to do this sort of upgrade is to have a script which pulls from instances API and pushes into the other.