Announcement

Collapse
No announcement yet.

Error installing

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

  • Error installing

    Just bought vbulletin 3.5.1 and trying to install on my server, I get this error

    Code:
    Invalid SQL:
    
    CREATE TABLE vb_deletionlog (
        primaryid INT UNSIGNED NOT NULL DEFAULT '0',
        type ENUM('post', 'thread') DEFAULT 'post',
        userid INT UNSIGNED NOT NULL DEFAULT '0',
        username VARCHAR(100) NOT NULL DEFAULT '',
        reason VARCHAR(125) NOT NULL DEFAULT '',
        PRIMARY KEY (primaryid, type)
    );
    
    MySQL Error  : All parts of a PRIMARY KEY must be NOT NULL;  If you need NULL in a key, use UNIQUE instead
    Error Number : 1171
    Date         : Tuesday, November 8th 2005 @ 06:50:42 PM
    Script       : http://www.xxx.xx/forum2/install/install.php?step=3
    Referrer     : http://www.xxx.xx/forum2/install/install.php?step=3
    IP Address   : 213.45.22.172
    Username     : 
    Classname    : vb_database
    MySQL is version 3.23.58 and PHP is version 4.3.10 so it's not a problem of an older version of php or mysql.

    Any suggestion?

    Thanks

  • #2
    Problem solved. There are two error in the mysql-schema.php inside the install folder. These two

    Code:
    $schema['CREATE']['query']['moderation'] = "
    CREATE TABLE " . TABLE_PREFIX . "moderation (
        threadid INT UNSIGNED NOT NULL DEFAULT '0',
        postid INT UNSIGNED NOT NULL DEFAULT '0',
        type ENUM('thread', 'reply') NOT NULL DEFAULT 'thread',
        PRIMARY KEY (postid, type),
        KEY type (type)
    )
    ";
    $schema['CREATE']['explain']['moderation'] = sprintf($vbphrase['create_table'], TABLE_PREFIX . "moderation");
    are missing the NOT NULL definition that I've put in bold. Inserted the NOT NULL the setup went ok.
    Code:
    $schema['CREATE']['query']['deletionlog'] = "
    CREATE TABLE " . TABLE_PREFIX . "deletionlog (
        primaryid INT UNSIGNED NOT NULL DEFAULT '0',
        type ENUM('post', 'thread') NOT NULL DEFAULT 'post',
        userid INT UNSIGNED NOT NULL DEFAULT '0',
        username VARCHAR(100) NOT NULL DEFAULT '',
        reason VARCHAR(125) NOT NULL DEFAULT '',
        PRIMARY KEY (primaryid, type)
    )
    ";
    $schema['CREATE']['explain']['deletionlog'] = sprintf($vbphrase['create_table'], TABLE_PREFIX . "deletionlog");

    Comment


    • #3
      This is a problem that have been reported a few times before. The official answer is that vBulletin 3.5 don't support MySQL 3.x aymore. Consider upgrading to a 4.x version.
      Want to take your board beyond the standard vBulletin features?
      Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

      Comment


      • #4
        Thanks Marco but the vb site state

        vBulletin is designed to run on every server that has PHP 4.1.0 or greater and MySQL 3.23.33 or greater installed

        And I've bought vb to run on my server that has MySQL version 3.23.58 and PHP version 4.3.10....

        Could I guess that the other problem I've asked for is another problem of an old mysql version?

        Comment


        • #5
          Same issue here -

          We are extremely disappointed that this critical criteria was not provided prior to purchasing the product.

          Several major ISP's and CoHosting facilities are running MySQL 3.23.X as default. Customers should know that Vbulletin 3.5.1 requires MySQL 4.x.

          Comment


          • #6
            I know that there are a lot of sites running vB3.5 with MySQL3 and they run without any major problems.

            I suggest you wait on a Jelsoft Staffmember to give an official answer on this.
            Want to take your board beyond the standard vBulletin features?
            Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

            Comment


            • #7
              We are aware of the current issues with older versions of MySQL. Our developers are working on a fix. The issue is caused because of incompatibilities with the 3 series of MySQL and the 5 series of MySQL and how they want the queries to be structured.

              Aside from the workaround above, I would suggest installing vBulletin 3.5.0 and then immediately upgrading to 3.5.1 on new installations if you are using an older version of MySQL. Our documentation including requirements has been updated to reflect a higher minimum version but those requirements will affect the next major version.
              Translations provided by Google.

              Wayne Luke
              The Rabid Badger - a vBulletin Cloud demonstration site.
              vBulletin 5 API - Full / Mobile
              Vote for your favorite feature requests and the bugs you want to see fixed.

              Comment


              • #8
                vBulletin 3.5.x require a minimum of 3.23.33 as you've noted. The problem you've encountered is simply a bug that I introduced while trying to bring about greater Mysql 5 compatibility.

                Comment


                • #9
                  Originally posted by MarcoH64
                  This is a problem that have been reported a few times before. The official answer is that vBulletin 3.5 don't support MySQL 3.x aymore. Consider upgrading to a 4.x version.
                  Where is this official?

                  Comment


                  • #10
                    http://www.vbulletin.com/features.php (see the minimum requirements on the left).

                    System RequirementsMinimumPHP 4.1.0
                    MySQL 4.0.12
                    RecommendedPHP 4.4.1 or 5.0.5 or later
                    MySQL 4.0.26 or later
                    Should i be telling you this?
                    Want to take your board beyond the standard vBulletin features?
                    Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

                    Comment


                    • #11
                      uh oh Floris loses :O

                      Anyways, I also get this problem on my new server. Quite annoying. I hope I can get a 4 series working.

                      Comment


                      • #12
                        Floris is correct, as I posted above. We still support 3.23 with 3.5.x.

                        3.6 may see us drop support for 3.23

                        Comment


                        • #13
                          There is no winning or loosing here.

                          Seems the minimum requirements on the features page is already edited to prevent people from having problems in the future when upgrading.

                          The developers are always right in this. If Freddie say that it is still officially supported then it is (and if you wish, i loose )
                          Want to take your board beyond the standard vBulletin features?
                          Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

                          Comment


                          • #14
                            We're not here to hold be right or wrong battles, we're here to provide support

                            Comment


                            • #15
                              so... what's the answer

                              Hello,

                              I've just bought the vBulletin and got this error in the 2nd step installing. I'm so disapointed.

                              I've read this post of all the suggestions but am confused as to which is the best answer.

                              Can someone tell me which to do to get around this error so my bulletin will get installed? I've already asked my hosting if they offer higher version of sql.

                              ty so much,
                              Last edited by studiodrama; Fri 11 Nov '05, 12:28pm.

                              Comment

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