Watermaps

**cavedude** · #1 01-31-2008, 06:06 AM

No, those scripts will not be updated because those tables are no longer needed and people still have them. Data in this community has the way of sticking around, and confusing people years later, so this is my way of purging the system

Just source with verbose mode off (drop the -v) and it'll skip right past them. *Releases will not have this issue, only tables contained in the release will be sourced/droped*

rule_values is a player script because it is a table commonly changed by the end user. Having it as a system table would piss people off with tweaked rulesets. Having a third category is not an option because I am too lazy to update PEQ's script, and quite frankly having two scripts confuses many people as is, adding a third would make matters worse.

Yes, any and all tables can be sourced in separately. rule_values, commands, variables, etc. I don't recommend doing this for system tables because obviously many tables are linked together, so sourcing in one without the other will create errors and/or features to not function.

cubber · #2 01-31-2008, 06:22 AM

Thanks for the reply, it is understandable that you want to cause as little confusion as possible.

So if I understand you correctly... If I just source in the new rules_values.sql to my updated database, I will be good to go with a fully updated database without any issues? If I made any changes to my old rules_values table I obviously will have to go back and make those changes again because they will get reset to default.

But sourcing in anything that is in the load_system.sql file by itself will cause problems...

I just want to be clear before I do this to my year old database.

cubber · #3 01-31-2008, 07:10 AM

One other question, I noticed that tables like variables and commands have been updated as well. Is it worth updating these to the newest revisions also or are the updates mostly comments and such? If so a list of tables that are considered "player scripts" that should be watched for changes and updated manually would be helpful.

Thanks again for your help!

**cavedude** · #4 01-31-2008, 08:02 AM

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 · #5 01-31-2008, 08:13 AM

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** · #6 01-31-2008, 08:29 AM

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 · #7 01-31-2008, 08:37 AM

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.

circuitdragon · #8 01-31-2008, 12:46 PM

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?