Life is Feudal Official Forum

[Terroth]

Hey everyone!

I have a feeling that the DB on my server is not being automatically updated after the patch.sql updates.

Claim timers are still set to 12h, bone glue is still a 60 requirement without changing the recipe table in the db manually to 0, also drying racks are still shooting off internal error with wolf.

I want to be very careful with my players db data, as we play with very slow skill progression, and not do anything I don't fully understand in "wonder if this works?" mode. Also interrupt play time as little as possible.

Any ideas?

[Shu]

I suppose you do have the HeidiSQL tool installed alongside MariaDB, and you stopped the dedicated server. (Otherwise you might get inconsistent data in your backups.)

To backup your entire LiF DB:
1) Start HeidiSQL and connect to your DB
2) Select "Tools -> Database SQL Export"
3) In the left tree expand the root node and check the "lif_1" schema
4) On the right side leve the checkboxes empty
5) Under "Data" select "DELETE + INSERT"
6) Leave "Output" as "Single .sql file"
7) Enter a path and filename for your backup file
8) Press "Export" at the bottom of that window

To backup the stored procedures proceed in the same way, but instead of checking "lif_1" in the tree, expand "information_schema" and check the table "ROUTINES". Everything else stays the same, but make sure you give another filename or it will override your LiF data backup!


To apply the patch, go to "File -> Open SQL-file" in HeidiSQL. Locate your "patch.sql" file and open it.
Make sure you have the "lif_1" schema selected on the left, and run the script.
To do so, you need to click the little down-arrow right to the blue "play" button in the tool bar and select "send multiple queries in one go" (translated from German, may be called a bit differently). Otherwise running it would produce an error, but not destroy anything. Run the script then by clicking said blue play button.

If anything bad happened, you can restore your old DB using the same Open SQL-file function. Just load your exported backup files and run them. (You might be asked if it should be run directly, since opening it in the editor could be slow due to its size. Perfectly viable option.)
In both cases always make sure you selected the correct target schema on the left side before running the scrips.


If anything is still unclear, feel free to ask away.

[Terroth]

Thank you for the detailed reply!

So I take it I need to acquire patch 1.8's patch.sql file as well... Is there a ftp or something available for old patches?

By the way this issue with the SQL DB is with Bluefangsolutions, which otherwise have provided excellent service.

[Shu]

Oh okay, I have no clue how access and management is provided there, and what your possibilities are. I'm hosting my server at home. In that case you might rather rely on BlueFang's service.

[Terroth]

Your instructions will be fine, they offer full DB access, its definitely not patching the DB on updates though. I've had to manually change a lot of the patch.sql file myself.