Explore switching to database for storage

[AkeemAllen]

WikiGen currently uses raw JSON to store data. I've begun hitting several limitations of what's possible with this storage method. For example, I had to "shard" pokemon data among 10 files to prevent long save times. This is because I can't make granular/targeted updates to pokemon data without rewriting the entire json file.

If I'm giving users the ability to create fakemon, having this 10 "shard" structure isn't as ideal as using a traditional database.

This ticket is meant to explore what it would take transition to a database

[AkeemAllen]

Preliminary database structure

Item

• Name
• Base 64 sprite
• Effect

Nature

• Name
• Increased Stat
• Decreased Stat

Ability

• Name
• Effect

[AkeemAllen]

Findings

Will need to load in sqlite db file upon wiki's first creation. Can I create sqlite db's per wiki?

To create a db file per wiki, I may need to run initial migrations on a main.db file and then copy the file per wiki on wiki change load database.

[AkeemAllen]

intial plan of attack

• Have intial.db hold all of the default data, basically replacing the starting data folder with a single sqlite file.
• When a new wiki is created, copy that file to wiki with new name
• Update Items functionality to use db instead of json as a first test
• From rust side, read data from these sqlite dbs.

[AkeemAllen]

Instead of automatically marking an entry as modified or new, allow the creator to do this