Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Importer #9

Open
Frostshake opened this issue May 5, 2024 · 1 comment
Open

Data Importer #9

Frostshake opened this issue May 5, 2024 · 1 comment
Assignees
Labels
Data enhancement New feature or request

Comments

@Frostshake
Copy link
Owner

Frostshake commented May 5, 2024

Data importer for vmangos -> trinity database.

Ideally in the future support other source databases e.g tbc
Also import will need to be able to verify / check data.

Current plan for the database is:

  • Keep existing TC structure (or minimal changes)
  • Import data from external sources.

This will hopefully reduce duplicated work between projects, and make changes easier to update in the future.

Current strategy has been to try and 'merge' data into the existing database, but not sure how effective it actually is. To decide: continue 'merge' method, or erase all and replace.

Running import:

See contrib/vmangos_db_import python db_import.py python db_verify.py

Will likely require python files to be edited to update db connection and enable features (whole import is slow).

Require access to the trinity world db and the vmangos world db.

Manual files required for import:
BroadcastTexts1.csv
WorldSafelocs.json

Current world database with imports applied can be found at (29/12/2024):
https://drive.proton.me/urls/0MT2PR9ZJ8#Qfu8dNpBPd5w (world + hotfixes)
https://drive.proton.me/urls/Z3M3J6R4DW#TWj6uTj7yzl9 (characters)

@Frostshake Frostshake added the enhancement New feature or request label May 5, 2024
@Frostshake Frostshake self-assigned this May 5, 2024
@Frostshake
Copy link
Owner Author

Frostshake commented Oct 19, 2024

Done some more thinking on this since first starting the db import process. The 'merging' approach doesnt work as it isnt repeatable, as in, it gives slightly different results importing the same dataset.

Todo: need to define which tables will/will not be handled by import, and which tables need to be updated/generated by other means.

@Frostshake Frostshake mentioned this issue Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant