Page 1 of 1

important table sql update guide to updating your dspdb

Posted: Tue Apr 14, 2015 12:48 am
by Delaide
When an important table is updated in dsp, it can break your stuff.

Here is a step by step guide (Sorry, using navicat lite, although other database management software can do this too. But it is not always using the same command name)

Step 1. Download the appropriate sql update. Put it somewhere you can remember so you can select it later.

Step 2. Open your Navicat to your dspdb database. Make sure you have the database selected. Better if you can see the tables in the right panel.

Step 3. Right click your database and select "Execute Batch File..."
Step2.jpg
This will bring you to the sql batch file process.

Step 4. On this screen, click the ... and select your file.
Step3.jpg
Step4.jpg
Step 5. The file should now be loaded for processing. Click start.
Step5.jpg
This will run the sql update file and if everything is correct, you should see a message like this:
Step6.jpg
Your table should now be updated. Feel free to open the table in your dspdb to confirm that the new columns are there.

Re: important table sql update guide to updating your dspdb

Posted: Tue Apr 14, 2015 12:50 am
by Delaide
Table update for 4/14/2015 database update. Please use this file if your char_stats does not have pet_id, pet_type, pet_hp, pet_mp.
04142015sqlupdate.sql
(320 Bytes) Downloaded 164 times

Re: important table sql update guide to updating your dspdb

Posted: Wed Apr 15, 2015 8:47 pm
by stamcof
Excellent! Everything is working now. Thank you.

Re: important table sql update guide to updating your dspdb

Posted: Wed Apr 15, 2015 8:55 pm
by stamcof
One more quick question for future reference. Where do i download the appropriate sql update in the future?

Re: important table sql update guide to updating your dspdb

Posted: Wed Apr 15, 2015 11:03 pm
by Delaide
When the important tables change (We can just wipe and use git tables for the non-important so those will not need restored), if I am still around, I will attach here and use date referencing so you know if you built it before that date, but haven't applied, you can download. So, just look for future patches located in this thread.

Re: important table sql update guide to updating your dspdb

Posted: Tue May 12, 2015 9:04 pm
by Delaide
The 5/5/2015 broke more stuff: https://github.com/DarkstarProject/dark ... 2093c035cf
Please find the sql fix for the chars.sql table in your existing database.
lockstyle.sql
(70 Bytes) Downloaded 162 times
Please also ensure that you add the new table, char_style.sql, to your database.

The lockstyle code implementation is:

Code: Select all

ALTER TABLE chars ADD `isstylelocked` tinyint(1) NOT NULL DEFAULT '0';

Re: important table sql update guide to updating your dspdb

Posted: Tue May 12, 2015 11:28 pm
by stamcof
Awesome!

Re: important table sql update guide to updating your dspdb

Posted: Thu Aug 13, 2015 4:17 pm
by SwitchVII
They've done it again! Modified chars table and new char_merits table. Any help on this one or should I brave editing the table manually (shouldn't be too hard)?

Re: important table sql update guide to updating your dspdb

Posted: Thu Aug 13, 2015 6:21 pm
by kjLotus
SwitchVII wrote:They've done it again! Modified chars table and new char_merits table. Any help on this one or should I brave editing the table manually (shouldn't be too hard)?
all you have to do is run the merits migration tool after creating the char_merits table. you don't even have to remove the old merits column if you don't want to - nothing in that update will be a loss of information (just moved around), nor will it actually require any editing of existing character tables (since it just removes a column)

Re: important table sql update guide to updating your dspdb

Posted: Fri Aug 14, 2015 4:50 am
by Delaide
Sorry, in this case, since you need to run the merit converter before you update, I don't want to give an SQL file for removal of that column. Afraid someone would run it before updating their merits and end up without the merits, since all an SQL file would do is remove that specific blob. The last thing I want is a message saying "I ran your SQL, it deleted all my merits, and I didn't have a backup so they are lost".