Upgrade from version 1.7.0 database to version 2.0.0 NOT SUCCESSFUL

Question

Upgrade from version 1.7.0 database to version 2.0.0 NOT SUCCESSFUL

NoHoPeLess opened this issue 10 years ago · 7 comments

NoHoPeLess commented 10 years ago

Hello :D i go to the new 2.0 and result in this:

http://pastie.org/9742448

I use spigot 1.7.9 r0.2

SmallSansSerif · Answer 1 · 2014-11-25T16:24:33.000Z

I'll be following and waiting too as I'm using MySQL currently. Thanks for working on this plugin again :)

andune · Answer 2 · 2014-11-25T16:04:16.000Z

Ah, this would be because I only tested Sqlite locally for the DB upgrade. I lifted code from 1.7 I had done many months ago and assumed I had tested it on both MySQL and Sqlite way back, but I guess not.

I don't have my old test servers setup anymore, so I'll have to get another one running with MySQL and give this some local testing with debug on to fix. I'd suggest not trying 2.0 until I respond back here that the MySQL upgrade is tested and this problem is fixed.

Thank you for the bug report.

NoHoPeLess · Answer 3 · 2014-11-25T19:51:55.000Z

Yes thx and welcome back andune! You are a very great developer! Keep up your great work!

andune · Answer 4 · 2014-11-25T21:44:23.000Z

I believe this is fixed as of build 567 on Jenkins. I tested locally and it seems to work well for both MySQL and Sqllite.

As always, since this is beta and HSP is upgrading the HSP database for you, it's a good idea to make sure you have backups before testing the upgrade. I've tested it dozens of times and it works well for me, but it doesn't hurt to be extra careful.

Please give it a test and let me know if this is fixed in your environments as well.

SmallSansSerif · Answer 5 · 2014-11-25T21:45:23.000Z

ok will give it a go

SmallSansSerif · Answer 6 · 2014-11-25T22:27:13.000Z

The MySQL database seemed to upgrade fine and the log file was clean at startup. I was using my existing config file if that matters.

I did roll back to the old version until I can figure out why I was getting sent to the default server spawn after every login though. I'm using Multiverse with multiple worlds. Any thoughts as to why the spawn behavior would change? It mometarily would appear at the last known point and then I would appear at the server default spawn. Priorities?

andune · Answer 7 · 2014-11-26T09:24:55.000Z

SmallSansSerif: thanks for confirming MySQL upgrade is fixed. In the interest of keeping the issue log clean, please open a new issue on the other item you mentioned. If you can provide your config.yml as part of that report, I can see what strategies and configurations you have set and try to reproduce the issue locally.

Closing this issue as resolved based on my own tests plus confirmed successful MySql upgrade from someone else.

Share to