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.
|