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