Announcement

Collapse
No announcement yet.

Upgrade error 3.0.0 beta 6->7 upgrade5.php?step=2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Upgrade error 3.0.0 beta 6->7 upgrade5.php?step=2

    I am getting this error when upgrading from vB 2.3.2:

    Database error in vBulletin 3.0.0 Beta 6:
    Invalid SQL:
    ALTER TABLE user
    ADD autosubscribe SMALLINT NOT NULL DEFAULT -1

    mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '-1' at line 2
    mysql error number: 1064
    Date: Thursday 03rd of June 2004 06:48:26 PM
    Script: http://xxx/install/upgrade5.php?step=2


    I have tried everything possible (cleaned the db, indexes, etc) and no other (backup) db is available. I have ran it 3 times with the same error message

    Config:

    freebsd 5.1
    apache 2.0.46
    php 4.3.6_1
    mysql 4.1.1_2

    Any suggestion how to bypass this problem?

  • #2
    Problem has been resolved

    Edit the following 2 files: upgrade5.php & upgrade6.php

    Change:
    ADD autosubscribe SMALLINT NOT NULL DEFAULT -1

    To:
    ADD autosubscribe SMALLINT NOT NULL DEFAULT '-1'

    &

    Change:
    $query[] = "ALTER TABLE " . TABLE_PREFIX . "user CHANGE autosubscribe autosubscribe SMALLINT NOT NULL DEFAULT -1";

    To:
    $query[] = "ALTER TABLE " . TABLE_PREFIX . "user CHANGE autosubscribe autosubscribe SMALLINT NOT NULL DEFAULT '-1'";

    I am not sure why it happend but most likely it is a mysql config problem (as I am using the most current version)

    Comment


    • #3
      Your using the most current unstable version you should be using mysql 4.0.20 for the most current stable version, mysql 4.1 is differnt from mysql 4.0

      Comment


      • #4
        Any idea when support for MySQL v4.1.x (or even better, v5.x) will be implemented? I've got some stuff I am really wanting to use on v4.1.x and vBulletin play nice on 4.1.x

        Comment


        • #5
          Some time after MySQL 4.1.x becomes stable i would guess
          Last edited by Zachery; Thu 17th Jun '04, 8:57pm. Reason: stupid isp

          Comment


          • #6
            I have been using it on 4.1 for the past few weeks and it works perfectly!

            Comment

            widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
            Working...
            X