You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The library does not provide a way to insert data directly into a database, so something like the extract script actually in use would not be possible unless we edit the library.
Also, it does not provide any way to filter the fields and choose the ones to extract, so the full content of every dbc would be inserted.
So it's doable, with a bit of work. The second point is neglectable, but the first isn't unless the final user is supposed to import himself all the sql batch files generated by the library :P
Personally, while I agree that the current system is about as comfortable as a rock in a hard place (I wrote it ;) ), I do not see the need to add a full library (we will not be writing DBC files, will we?) for a step which is done ONCE during SETUP and will rarely, if ever require modification. IMHO the DBC format is simple and well-documented enough to not put any additional effort into this.
I have pushed an updated version of the DBC library accompanied by mappings for all 1.12 DBC files. There are a only five or six fields, which I could not resolve or cross-reference to other fields.
Instead of hardcoded DBC reading we should use timkurvers/wow-dbc library as it provides a clean interface for reading and writing DBC files.
The text was updated successfully, but these errors were encountered: