Then may select an older DB version from a dropdown list [DEST]
It may even select the DB version it is using now [ORIG]
And finally a Download button appears that outputs directly a zipped folder with both the basic DB and the updates merged in an “updates_from_ORIG_to_DEST.sql” file.
Not sure it was clear… By the way, what do you think about that?
Of course it is not, but think at db and updates, they’ve been distributed this way since the beginning. Are there any reason to not make simpler and faster things like these, which are done (manually) very frequently?
@Polaretto If you check the worldserver.conf file, you will see a couple of settings for automatically applying database patches. The steps are quite simple (even for those not compiling their own build, which I recommend they do since there is no official pre-compiled versions available) .
Download TrinityCore source (git pull { preferred method } / zip archive / whichever … ) * Edit the worldserver.conf, and if you didn’t compile your own, set the parameter for source folder to where TrinityCore source tree is. * Enable automatic database updates * Download (currently 6.02 from July 2015) latest build of the TDB * Import the auth and characters sql files into their respective databases from TrinityCore/sql/base * Import hotfixes and world from TDB sql files into their respective databases (inside the TDB download, not the TrinityCore source) * Start ./worldserver . Now as long as the settings / etc are all correct in worldserver, it will automatically merge new updates from that date forward from the sql patch files in the TrinityCore source that you downloaded in the first step. What I would suggest, is perhaps to include TDB in the sql path as part of the TrinityCore source tree. That would make things a bit easier than trying to load from different places, however there may be a logical reason for why the two projects remain segregated from each other.