Errors while server startup - https://imgur.com/a/rur4xdW (include server.cfg)
Yesterday i transferen json2mariadb, then i used cmd /bb migrate.
After that i changed config "JSON2MARIADB" to MARIADB.
WHen i startup server there is those errors, but everything looks working.
/bbox version (Mandatory)B臎啪铆m na: Paper
Verze BentoBox: 1.15.0
Datab谩ze: MARIADB
Worlds: Oneblock_world, world, world_nether
Addons:
Aoneblock 1.4.0
Border: 2.0.0
Chat: 1.0.5
Level: 2.4.1
Warps: 1.10.0
@tastybento this is the github issue where are old and new tables in database.
Could it be an issue with migration from json to mariadb?
https://cdn.discordapp.com/attachments/310623455462686720/763002234933346324/unknown.png
On discord you told me to delete that long names, so i did it.
But after server start one of that long names recreated again.
https://cdn.discordapp.com/attachments/310623455462686720/763005055870959636/unknown.png
So i it will throw error again after restart.
But everything seems to be working with short db tables, players didnt report any missing things.
@BONNe Yes, the migration command is a problem. I don鈥檛 think it is using the latest short names. I鈥檒l check it.
@kFxDaKing can you share the full name of the remaining long table because the graphic cut it off? Some addons still use long names, so it鈥檚 okay, but I would like to know what it is.
It is oneblock:
https://github.com/BentoBoxWorld/AOneBlock/issues/122
Hello, thanks for reply.
@kFxDaKing https://ci.codemc.io/job/BentoBoxWorld/job/AOneBlock/126/ uses the shorter named table. When used, it should migrate directly over. Take backups, and let me know if you see any issue.
Ill test it tomorow, thank you.
https://imgur.com/a/xTIkRpd
Cant load
Well, there was a longstanding bug in BentoBox where the tables were not being renamed. I do not understand how or why that happened so this is the root cause. You will need to use the latest BentoBox build.
If you do get an error, please share the full console log from start up (the zip file) so I can see what other errors are happening.
I'm closing this issue since it seems the bug has been solved.
@kFxDaKing Feel free to reopen/answer it if needed.