Forum

Results 1 to 4 of 4
  1. #1
    Join Date
    June 2010
    Location
    München
    Posts
    10

    update pfade von TS3 Server 3.0.10.3

    i'm currently running TS3 Server 3.0.10.3 on Windows Server and MariaDB 5.5.31 using the default ts3db_mysql.dll

    Default collation: latin1_swedish_ci
    default characterset: latin1

    Is it possible to do only the mariadb conversion described in releasenotes for 3.0.11 and direct upgrade to the latest version (3.0.13)?
    Or do i need to install every single version leleased since 3.0.10.3 ?

    BR
    XClaude

  2. #2
    Join Date
    June 2008
    Posts
    18,151
    utf8mb4_general_ci is a system requirement for the server, when you use MariaDB.
    It will not work without.

    You need to convert your database and then you can upgrade to the latest 3.0.13.6 without any other steps.
    You may make a backup of your database first and convert then.


    P.s Ich wunder mich warum der Titel deutsch ist, aber der Post english.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  3. #3
    Join Date
    June 2010
    Location
    München
    Posts
    10
    i just upgraded my database with the first script.
    i get the following warning:
    Code:
    14:30:56	ALTER TABLE instance_properties CONVERT TO CHARACTER SET 'utf8mb4', DEFAULT CHARACTER SET 'utf8mb4'	16 row(s) affected, 2 warning(s): 1071 Specified key was too long; max key length is 767 bytes 1071 Specified key was too long; max key length is 767 bytes Records: 16  Duplicates: 0  Warnings: 2	0.266 sec
    can this be ignored or can it be fixed with additional manual steps?

  4. #4
    Join Date
    December 2004
    Location
    RF
    Posts
    3,006
    "Default" charset/collation is not really relevant. MySQL long since supports per-table and even per-column collations.
    AFAIK, TS3 from the start is using UTF-8 (3-byte) encoding. It IS safe to convert existing database to utf8mb4, no data loss is expected, not even data alteration. (Backups are still your best bet to be safe.)
    Regarding that index issue, you'd have to google.
    I.e. this http://stackoverflow.com/a/1814594/1449366 answer discuss the origins and solutions of the mentioned warning.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 3
    Last Post: November 8th, 2012, 12:22 PM
  2. Replies: 5
    Last Post: October 24th, 2012, 04:02 PM
  3. Replies: 5
    Last Post: October 3rd, 2012, 12:58 PM
  4. Replies: 1
    Last Post: April 1st, 2010, 06:48 AM
  5. Update not querying to update server
    By Fha-Patch in forum Windows
    Replies: 1
    Last Post: January 20th, 2010, 03:11 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •