Queries database then scans corresponding SQL file, replacing values
in INSERT statements with data from the database.
Is not smart about which INSERT statement gets which data; line-end
comments can get shuffled around if SQL file INSERTs are out of order
or missing. If you're doing INSERT or DELETE operations, make sure
to add a blank "INSERT INTO `table` VALUES ();" or manually remove
the INSERT statement respectively before dumping tables.
MyISAM = table level locking, fast but not safe for multiple simultaneous writes
InnoDB = row level locking, slow, but is safe for multiple simultaneous writes
```
Features MyISAM InnoDB
Type Non-Transactional Transactional
Locking Table locking Row-level locking
Foreign keys No Yes
Table, index, data storage Three separate files Combined Tablespace
ACID No Yes
```
- Rebranding.
- Migrate to GitLab.
- Add support for database updates when using Docker.
- Give purpose to version.h (adjust minor version with client updates).
- Add an in-game `!ver` command.
- Remove references to AGPL.
Adds item_equipment.sql 21915-22113
Adds item_mods.sql 21909-22275
Also added zanmato_+1.lua for added effect dispel and tachi_suikawari.lua weapon skill (and fix tachi_kaiten.lua since it is 80% str, not 75%...)
Still have 53 items left to add (Will do on next PR)
Also fixed the weapon skill bug I accidentally created (having Final Paradise without having the items equipped) and spaced out the comments around the Kikoku fix so they are the appropriate position (column 51)
After a discussion with TeoTwawki, which took place after my previous submission, I removed the all jobs from Relic WSs. He has informed me that item mods handle the granting of the WS.
...also I'm fixing a typo I made earlier. Since I only did partial testing. Sorry!
-Added the main job restriction to all the quested WSs that did not have it, to all merit WSs, and to all Mythic/Empyrean WSs. When the quest/Mythic/Empyrean WSs are unlocked, they're supposed to only be used by the main job - PLD/RDM should not be able to use Death Blossom, for example. Though, I do realize that currently such WSs do not have to be unlocked...
-Added GEO to all non-special staff WSs.
-Added WAR/BST/BLM to Infernal Scythe
-Removed RUN from Scourge. Seriously?
-Some other misc. WSs did not have the main job restriction that they're supposed to have, so I added that.
-Bumped down the ranged Empyrean WSs to 300 skill for the sake of consistency.
-While I'm unsure how Relic WSs are given to players regardless of skill when equipped with a Relic weapon, I added a main job restriction to them so you can't have say... BLU/RDM able to use Knights of Round without a Relic.
CORE: Updated capAllSkills to include blu and geomancy.
SCRIPTS: Updated @capskill command to include geomancy. Updated status.lua with Action IDs.
CORE / SQL: Added new column to skill_caps.
SQL: Added non-job-specific traits to Rune Fencer and Geomancer. Added weapon skills to Rune Fencer and Geomancer.
