Quote:
Originally Posted by iluvseq
I have yet to see any of those warnings. Other than the one I posted after I figured it out the hard way.
Regardless, that has nothing to do with the fact that the update_db.pl script parses the configuration file for <host> and then ignores it, only working on localhost unless you set the MYSQL_HOST environment variable.
This is a bug in the script, regardless of which peq db one uses (or even if one doesn't use peq at all!)
|
Wouldn't necessarily call it a bug.
It pulls it down automatically because I've set it that way for a while because at one point the script wasn't capable of checking itself for updates by being passed parameters by the source, could probably change that soon.
Also, why are you using multiple hosts? It's far unecessary unless you actually have load to match the necessity.
98% of the folks who run the script aren't going to need a host option and would simply run it on their database server.
Updated, you're welcome.
https://github.com/EQEmu/Server/comm...a6e1e00cc91214
And
Quote:
|
Even then, the script still doesn't fully update the database (coming from peqbeta_2014-10-11-02:01.sql) as apparently that database is missing some core tables like character_buffs so there are 8 required updates which fail to apply. Not really a problem with the script, per-se, although I'm surprised there isn't a simple empty schema included with the source that one could apply to build an empty, clean and current database so that this whole patch process wouldn't be necessary for a brand new installation. Relying on PEQ to provide the base schema seems silly.
|
This has to do with PEQ dumps, the schema update does exactly what it needs to do and PEQ missing tables is another issue in itself. I will notify those who oversee those dumps.
Threaded Mode
