Commit graph

11 commits

Author SHA1 Message Date
Corey Sotiropoulos
f202e592e7 [sql] Speed up Aria table inserts
See:
https://mariadb.com/kb/en/aria-storage-engine/
2024-01-11 22:33:23 -05:00
Zach Toogood
24f35c4c5e [sql] Replace MyISAM engine with Aria 2024-01-04 18:43:36 +00:00
Zach Toogood
ca3bdd22fe [SQL] Add COLLATE=utf8mb4_general_ci to all tables 2024-01-04 18:25:12 +00:00
Corey Sotiropoulos
d92c54d1b4 [dbtool] Add function to dump DB to SQL files
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.
2023-08-23 22:50:08 -04:00
Zach Toogood
edc817a2d7 [db] Make all tables CHARSET=utf8mb4 2023-02-05 21:13:32 +00:00
TeoTwawki
dd02066118 Convert tables that are never written to back to MyISAM. Only tables we write to need InnoDB.
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
```
2021-11-10 08:09:45 -05:00
Zach Toogood
9e4993893d Migrate all SQL tables from MyISAM to InnoDB 2021-02-05 17:07:08 +02:00
TeoTwawki
8209f73159 Line ends, round 2. Fight! 2016-01-16 01:26:33 -05:00
atom0s
d91549b194 SQL: Changed all tables to use MyISAM for much improved import / query times.
SQL: Changed all tables to use the charset of utf8.
2014-01-09 03:20:52 +00:00
samuel.l.hyman
4d21ce5fb6 Skillchain progression changes. You can no longer continuously chain Light and Darkness skillchains.
CORE: 
* Changes to the way skillchains are handled.  
  - now follow primary, secondary, tertiary chain rules (see wiki for details.)
* Also added in the persistence of effect SubPower and Tier for effects that are being read and written to the database.

SCRIPT:
* Removed skillchain.lua and replaced it with magicburst.lua
  - This filename describes what it does a bit clearer.
  - Contains the new method for determining what elements link with which skillchains.

SQL: 
* char_effects.sql added the two new columns to keep SubPower and Tier of an effect saved.
* skillchain_damage_modifiers.sql added 4th level of skillchain. (Light + Light, Dark + Dark)
  - Also added in values for magic burst bonus, these still aren't used yet as the lua script calculates the bonus out.
* weapon_skills.sql added three new columns for skillchain progression, primary_sc is the first effect that will try to link, followed by secondary, then tertiary.  A side note is the element column was previously used to store these values but lacked a method to store the priority.  This column is now free for use to store a weaponskills elemental damage attribute for upcomming elemental damage weaponskills.
2012-07-22 22:50:33 +00:00
samuel.l.hyman
c9853d3a24 CORE: Changes to the core to allow skill chains to do damage. Tracks the number/level of chains occurring and modifiers damage accordingly. Also adjusts damage based off monster resistances. Now populating monster resistances from the database. Also added new
SQL: Added table from skillchain_damage_modifiers.sql
     - Used to determine skill chain count/level damage modifiers and up-coming magic burst damage bonuses.

SCRIPTS: Added new modifiers for skill chain damage gear/effects.
2012-07-06 22:24:03 +00:00