Skip to content

Commit

Permalink
moves playtime tracking change entry below header
Browse files Browse the repository at this point in the history
  • Loading branch information
Jordie0608 authored Aug 20, 2017
1 parent 3d8c7ac commit f2e5cce
Showing 1 changed file with 9 additions and 11 deletions.
20 changes: 9 additions & 11 deletions SQL/database_changelog.txt
Original file line number Diff line number Diff line change
@@ -1,3 +1,12 @@
Any time you make a change to the schema files, remember to increment the database schema version. Generally increment the minor number, major should be reserved for significant changes to the schema. Both values go up to 255.

The latest database version is 3.1; The query to update the schema revision table is:

INSERT INTO `schema_revision` (`major`, `minor`) VALUES (3, 1);
or
INSERT INTO `SS13_schema_revision` (`major`, `minor`) VALUES (3, 1);

----------------------------------------------------

20th July 2017, by Shadowlight213
Added role_time table to track time spent playing departments.
Expand All @@ -7,21 +16,10 @@ CREATE TABLE `role_time` ( `ckey` VARCHAR(32) NOT NULL , `job` VARCHAR(128) NOT

ALTER TABLE `player` ADD `flags` INT NOT NULL default '0' AFTER `accountjoindate`;

UPDATE `schema_revision` SET minor = 1;

Remember to add a prefix to the table name if you use them.

----------------------------------------------------

Any time you make a change to the schema files, remember to increment the database schema version. Generally increment the minor number, major should be reserved for significant changes to the schema. Both values go up to 255.

The latest database version is 3.0; The query to update the schema revision table is:

INSERT INTO `schema_revision` (`major`, `minor`) VALUES (3, 0);
or
INSERT INTO `SS13_schema_revision` (`major`, `minor`) VALUES (3, 0);

----------------------------------------------------
28 June 2017, by oranges
Added schema_revision to store the current db revision, why start at 3.0?

Expand Down

0 comments on commit f2e5cce

Please sign in to comment.