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

Dbcsql #442

Open
wants to merge 28 commits into
base: master
Choose a base branch
from
Open

Dbcsql #442

wants to merge 28 commits into from

Conversation

cyberium
Copy link
Member

@cyberium cyberium commented Mar 12, 2021

🍰 Pullrequest

Remove support for dbc files and support downloading them from db instead.

Proof

  • None

Issues

Allowing to have them in db will open a new world of possibilities to fix some specific case that was not or at least more difficult to do before.
Translations already included.

How2Test

  • download this sql file
  • apply it to tbcmangos database
  • Build this core same way as usual.
  • run and enjoy.

Todo / Checklist

  • nothing yet but hopping to get some constructive comments

Yes this will be ported to other core when this PR will be merged.

Added dbc format
Added new SqlStorage instance for each DBC
Added loading part.
Make it easier and less prone to errors.
Will make it easier to replace dbcstore by sqlstore.
Make it more compatible wiht c++ iterator standard.
silent a casting warning.
- sCreatureDataAddonStorage
- sCreatureInfoAddonStorage
- sCreatureModelStorage
- sEquipmentStorage
- sEquipmentStorageRaw
- sPageTextStore
- sItemStorage
- sInstanceTemplate
- sWorldTemplate
- sConditionStorage
- sSpellTemplate
- sFactionStore
- sCreatureConditionalSpawnStore
Now we are able to define the index in the format and it can not be the first column.
This is needed for AreaTable. However we might need to double check why its done that way for that table.

Rremoved the need to define the name of the column as an index because code can find it using the provided format.

Added the support for table that have no index like gtcombatratings.
using n/d to define the index and removing column name.
@ClassicW
Copy link

the idea is very interesting and supported by our team.

@cala
Copy link
Contributor

cala commented Jun 27, 2021

the idea is very interesting and supported by our team

If you have a team, feel free to also open pull requests and not only issues. More man power would be appreciated.

@al3xc1985
Copy link

@cyberium is there anything else that must be implemented before this? or u are planing in the near future to implement it?

@cyberium
Copy link
Member Author

Not sure yet what to do with that

@al3xc1985
Copy link

al3xc1985 commented Jan 9, 2022

well, I supose that your intention was to make things easier for scripting and modifying data for unreacheable cases. Reading through the dbc structure file, in my little j=knowledge, I was some stuff that were not yet implemented, or unk the purpose of those collumns.
Wouldn't it be easier to implement all the future data with this patch? I mean everything that will be added, I GUESS, that it will be easier to adjust from your point of developer and later db devs.

Also loading them from db is way faster, it would give a slight boost to the server (my opinion)

So what do u say @cyberium ?

P.S. Just an opinion, nothing mandatory, cause I am no developer and my knowledge is resumed to testing and reading on google

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants