Automatic Database Upgrade and Versioning

[ghanja]

Is there a parameter world can be passed to either make a users preferred choice and/or completely say "not right now go away" ?

Confused because you stated:

When World boots up, it will start this check process by pulling down scripts from Github if you don't have them, this process happens transparent to the user

but then what reads to be a slight contradiction:

When you have updates that need to be made, you probably shouldn't be booting up anyways.

Interrupting the World process seems, well, a little pushy. <shrug> You asked for opinions, there ya go.

[Akkadius]

These are required database scheme updates and if you are updating your binaries you are also going to want your schematic to reflect so what you're saying doesn't make sense.

Adding a skip check parameter to world can be done for those who would like the choice. But the point is to have it so most users will notice that there is an upgrade needing to be done with the database side. It really takes seconds to do and you won't have to see it until you update your source with another schema change.

Also what you may not be seeing as well is that if your schema is up to date, world will still boot up uninterrupted. if world boots up and their binary DB version is greater than you local than you would want to update otherwise you could have major things flat out not work.

Anything can be added to it at this point it's pretty easy. Most of the heavy lifting is done and it was a lot of work in a short amount of time mainly because I've had a lot of time to think about it.

[ghanja]

Originally Posted by Akkadius

These are required database scheme updates and if you are updating your binaries you are also going to want your schematic to reflect so what you're saying doesn't make sense.

Halting the running of World waiting for user input was the gist of what I was making comment about.

Made sense to me.