Clean up World Database

[Kitzunu]

Describe your feature request or suggestion in detail

• 1st PR to just introduce the new Databases acore_dbc acore_module https://github.com/azerothcore/azerothcore-wotlk/pull/16943
  • acore_dbc - To hold all *_dbc tables
  • acore_module - a placeholder database module that can use instead of querying custom tables into acore_world. Makes it easier for users to find module tables and to keep acore_world to just "base" stuff
• 2nd PR to move all *_dbc tables from acore_world to acore_dbc except spell_dbc
• 3rd PR to rework spell_dbc
  • into serverside_spells table with only the bare minimum amount of columns needed for serverside spells in acore_world (Should be around 94 columns iirc).
  • Move the empty spell_dbc with its 234 columns into acore_dbc

---

• https://github.com/azerothcore/azerothcore-wotlk/issues/754
  • An acore_string table of sorts for custom strings used in modules could be provided by default in acore_module

[walkline]

I don't know much about the coupling of dbc and modules with the world DB. However, separating this data would make it impossible to use JOIN and other operations between the two databases. Would this not be an issue?

[Kitzunu]

The module one is more of a placeholder and will not be used by this repo at all, it is just for independent modules to use it instead of world, just to keep everything clean.

majority of _dbc files are just empty and act like an override to the .dbc files. and do not in any way operate with other tables

[walkline]

Understood about dbc, thanks.

Will module developers have the option to choose between the world DB (if their tables are coupled with world) and the modules DB (if they are independent)?

[Kitzunu]

Of course.

You could even just store everything in acore_auth if you desired 😅 Nobody can dictate what a module should do.

the main reasoning behind it was to clean up world db and to make it easier for module users to find the module-specific tables

[michaeldelago]

acore_module - a placeholder database module that can use instead of querying custom tables into acore_world

big fan

It'll probably be a good bit of time before most popular modules switch databases (but might be something we can wrangle through creating a PR with a script) but I think this is overall a good idea.

same with the dbc DB, it just kinda feels like noise when I'm scrolling through the databases