When eqemu moved to git, the convention of updates went from "revisions" to "date/time", the last peq db release was during the svn phase of eqemu, so the convention is still "revisions" but there are no more updates from eqemu svn for the 2506 peq db, so now you just need to source in the git updates that are sorted by date in the /sql/git directory...
One place you "will" have issues is mercs, as for some reason, you still need to import the OLD merc updates to fix issues with the 2506 db, including a foreign key issue with one of the tables..Best bet is to dump all the merc tables from the 2506 db then import the merc "optional" but "now REQUIRED" updates (2380_optional_merc*) from svn sql directory.
If you just try to apply the git updates to an unedited 2506 db you will have import errors because of the aforementioned foreign key issue...
This issue and confusion should go away when peq releases an updated db with the proper table structure for mercs..
So long answer shortened Cyndy, for a 2506 peq db, the updates to new pulled code are in the sql/git directory with a "date" naming convention, as the new git code does not use "revisions" as per the old svn..
|
Threaded Mode
