Watermaps

[cavedude]

Yep, you are completely correct.

The only player table that would see any real updates is rule_values. commands, launcher, launcher_zones, rule_sets and variables are tables that are also easily changed, but they won't be updated by PEQ. They are all pretty much one time setup tables.

[cubber]

Just to be 100% clear and to sum up the thread to mark it solved:

So whenever I update the database via cvs by using load_system.sql, I can also safely update the following tables manually without any repercussions on my character info or my system as long as I take note of any values that I modified and reapply them accordingly?

rule_values
commands
launcher
launcher_zones
rule_sets
variables

I take it that I need to drop the old table first then source in the new ones?

Thanks for clarifying this

[cavedude]

Yep, that's correct. If I were to make a third sql script, those would be the exact tables within in. I've fiddled with the idea of having system, player, and variables scripts, but as I said the third script may put many noobs over the top.

You don't actually need to drop the tables before hand, either. The sql files will drop the table if it exists, re-create the table, and source the data for you.

So, you'd first source drop_system.sql, then load_system.sql, then rule_values.sql, variables.sql, etc. Make sure you don't have -v when you run mysql so any errors will be ignored and flipped past. -v is only good when you're merging, creating new queries, or if you are having problems sourcing. Otherwise, it's best to leave it out.

[cubber]

Thanks. I did not realize that for the -v option. Every guide I have used always threw that flag in so I just went with it. I bet the sourcing is quicker without the verbose flying across the screen too.

[cubber]

So the 3rd script would probably look something like this?

source rule_values.sql;

source commands.sql;

source launcher.sql;

source launcher_zones.sql;

source rule_sets.sql;

source variables.sql;

[cubber]

I named that script update_variables.sql and ran it in the cvs directory. It worked perfectly. A few key things to note to those that try it:

You will have to Insert LoginType into the variables table again and set it to MiniLogin if you are using minilogin. I found that this entry was not in the new table.

I also had to rename zone in the launcher table to the name of my launcher that my start script calls. I guess you could also change the name in your start script to zone if you wanted.

and I had to adjust a few values in rules_values to get them back to the way I had them.

I guess if you changed any of the values in the commands table you would need to go back and edit that again too. PHPMyAdmin and a printer really help!

[cavedude]

Originally Posted by cubber

You will have to Insert LoginType into the variables table again and set it to MiniLogin if you are using minilogin. I found that this entry was not in the new table.

Forgot about that! I cleaned up the variables table some, and added some missing variables, including that one. That'll appear the next time I update CVS.

[circuitdragon]

I really hope I am not going to cause any more confusion here, but just a few quick questions. I have made CVS as my way of getting updates for PEQ. Now, maybe I am over working myself on this here, but I skip the "drop_system", "Load_system" and such, and instead only source the sql's that have a newer time stamp. Thus far its not had any issues, just trying to figure if I have made bad habits. Next question is, which is better, to download the PEQ databse from ProjectEQ's site, or...is the CVS the newest possible in any scenerio?