Announcement

Collapse
No announcement yet.

Database Error:1709

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

  • Wayne Luke
    replied
    There shouldn't be any memory tables in vBulletin 5.

    But yes, your tables should use a dynamic row format as well. This should be the default in MySQL.

    Leave a comment:


  • StarShaper
    replied
    Originally posted by Wayne Luke View Post

    The proper fix for this error is to set the innodb_large_prefix variable to On.

    https://dev.mysql.com/doc/refman/5.7...b_large_prefix

    This value is on by default in MySQL 5.7.7 and higher.
    Did not help!

    My MySQL Version is 5.6.

    innodb_large_prefix variable was set to On.

    I had to do it like I said above. And this is also the solution, which could be found on various sites in the internet.

    Leave a comment:


  • Wayne Luke
    replied
    Index column size too large. The maximum column size is 767 bytes.
    The proper fix for this error is to set the innodb_large_prefix variable to On.

    https://dev.mysql.com/doc/refman/5.7...b_large_prefix

    This value is on by default in MySQL 5.7.7 and higher.

    Leave a comment:


  • StarShaper
    replied
    I successfully upgraded to vB 5.

    I had to change "functions_installupgrade.php".

    Change this lines:

    PHP Code:
    //prefer innodb to memory type even for "memory" tables. The memory type
        //has locking issues similar to MyISAM and InnoDB will use memory caching
        //anyway for high traffic tables like session
        
    if ($innodb)
        { 
    // Otherise try Innodb
            
    return 'InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC';
        } 
    Last edited by StarShaper; Sun 10th Feb '19, 7:46am.

    Leave a comment:


  • StarShaper
    replied
    Same issue here!

    Trying to upgrade from 4 to 5. Getting this error:

    PHP Code:
    An error has occurred with your databasePlease contact vBulletin Support for assistance.

    Module500a1Step 3 Database Error:1709

    Index column size too large
    The maximum column size is 767 bytes.

    Query:   CREATE TABLE vbulletin_routenew (  routeid int(10unsigned NOT NULL AUTO_INCREMENT,  name varchar(100) DEFAULT NULL,  redirect301 int(10unsigned DEFAULT NULL,  prefix varchar(200NOT NULL,  regex varchar(400NOT NULL,  class varchar(100) DEFAULT NULL,  controller varchar(100NOT NULL,  action varchar(100NOT NULL,  template varchar(100NOT NULL,  arguments mediumtext NOT NULL,  contentid int(10unsigned NOT NULL,  guid char(150) DEFAULT NULL,  PRIMARY KEY (routeid),  KEY regex (regex),  KEY prefix (prefix),  KEY route_name (name),  KEY route_class_cid (class, contentid) ) ENGINE InnoDB 
    innodb_large_prefix is on!

    Leave a comment:


  • Wayne Luke
    replied
    Server OS is not relevant. We use some variant of Linux. The important things are the web server (we use Apache with mod_php), PHP (PHP 5.6.30 here), and database (MySQL 5.6.35).

    Your new error occurs much earlier in the database creation cycle than the previous error. Did you make any changes other than the ones listed above?

    MariaDB should be a drop in replacement for MySQL and your version is based on MySQL 5.6 with some MySQL 5.7 patches tossed on top.

    You will probably need to open a support ticket with FTP and Database Access so we can see what is going on behind the scenes.

    Leave a comment:


  • Djinni2
    replied
    = innodb_large_prefix is on

    Module: install, Step 2 Database Error:1064

    You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 8

    Query:
    CREATE TABLE access ( userid INT UNSIGNED NOT NULL DEFAULT '0', nodeid SMALLINT UNSIGNED NOT NULL DEFAULT '0', accessmask SMALLINT UNSIGNED NOT NULL DEFAULT '0', PRIMARY KEY userid (userid, nodeid) ) ENGINE



    question What a server os actually runs here (vbulletin.com/forum/)

    Leave a comment:


  • Wayne Luke
    replied
    Seems this is a bug in the MySQL code that your version of MariaDB is based on.You have to have the server administrator set innodb_large_prefix to On for your database server configuration.

    If that is not possible, you will need to remove these lines from core/install/mysql-schema.php for the install process:

    Code:
        INDEX node_lastauthorid(lastauthorid),
        INDEX node_lastcontent(lastcontent),
        INDEX node_textcount(textcount),
        INDEX node_ip(ipaddress),
        INDEX node_pubdate(publishdate, nodeid),
        INDEX node_unpubdate(unpublishdate),
        INDEX node_parent(parentid),
        INDEX node_nextupdate(nextupdate),
        INDEX node_lastupdate(lastupdate),
        INDEX node_user(userid),
        INDEX node_oldinfo(oldcontenttypeid, oldid),
        INDEX node_urlident(urlident),
        INDEX node_sticky(sticky),
        INDEX node_starter(starter),
        INDEX node_approved(approved),
        INDEX node_ppreview(public_preview),
        INDEX node_showapproved(showapproved),
        INDEX node_ctypid_userid_dispo_idx(contenttypeid, userid, displayorder),
        INDEX node_setfor_pubdt_idx(setfor, publishdate),
        INDEX prefixid (prefixid, nodeid),
        INDEX nodeid (nodeid, contenttypeid),
        INDEX contenttypeid_parentid (contenttypeid, parentid),
        INDEX node_featured(featured),
        INDEX node_inlist(inlist)
    You would have to manually add these indexes back after the install completes.

    Leave a comment:


  • Djinni2
    replied
    mysql Ver 15.1 Distrib 10.1.21-MariaDB, for Linux (x86_64

    I can not write in the English area

    Leave a comment:


  • Wayne Luke
    replied
    None of those indexes should be above the limit. What version of MySQL are you using?

    Leave a comment:


  • Djinni2
    started a topic Database Error:1709

    Database Error:1709

    New install Vbulletin 5.2.6

    An error has occurred with your database. Please contact vBulletin Support for assistance.
    Module: install, Step 2 Database Error:1709
    Index column size too large. The maximum column size is 767 bytes.
    Query:

    CREATE TABLE node ( nodeid INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, routeid INT UNSIGNED NOT NULL, contenttypeid SMALLINT NOT NULL, publishdate INTEGER, unpublishdate INTEGER, userid INT UNSIGNED , groupid INT UNSIGNED, authorname VARCHAR(100), description VARCHAR(1024), title VARCHAR(512), htmltitle VARCHAR(512), parentid INTEGER NOT NULL, urlident VARCHAR(512), displayorder SMALLINT, starter INT NOT NULL DEFAULT '0', created INT, lastcontent INT NOT NULL DEFAULT '0', lastcontentid INT NOT NULL DEFAULT '0', lastcontentauthor VARCHAR(100) NOT NULL DEFAULT '', lastauthorid INT UNSIGNED NOT NULL DEFAULT '0', lastprefixid VARCHAR(25) NOT NULL DEFAULT '', textcount mediumint UNSIGNED NOT NULL DEFAULT '0', textunpubcount mediumint UNSIGNED NOT NULL DEFAULT '0', totalcount mediumint UNSIGNED NOT NULL DEFAULT '0', totalunpubcount mediumint UNSIGNED NOT NULL DEFAULT '0', ipaddress CHAR(15) NOT NULL DEFAULT '', showpublished SMALLINT UNSIGNED NOT NULL DEFAULT '0', oldid INT UNSIGNED, oldcontenttypeid INT UNSIGNED, nextupdate INTEGER, lastupdate INTEGER, featured SMALLINT NOT NULL DEFAULT 0, CRC32 VARCHAR(10) NOT NULL DEFAULT '', taglist MEDIUMTEXT, inlist SMALLINT UNSIGNED NOT NULL DEFAULT '1', protected SMALLINT UNSIGNED NOT NULL DEFAULT '0', setfor INTEGER NOT NULL DEFAULT 0, votes SMALLINT(5) UNSIGNED NOT NULL DEFAULT '0', hasphoto SMALLINT NOT NULL DEFAULT '0', hasvideo SMALLINT NOT NULL DEFAULT '0', deleteuserid INT UNSIGNED, deletereason VARCHAR(125), open SMALLINT NOT NULL DEFAULT '1', showopen SMALLINT NOT NULL DEFAULT '1', sticky TINYINT(1) NOT NULL DEFAULT '0', approved TINYINT(1) NOT NULL DEFAULT '1', showapproved TINYINT(1) NOT NULL DEFAULT '1', viewperms TINYINT NOT NULL DEFAULT 2, commentperms TINYINT NOT NULL DEFAULT 1, nodeoptions INT UNSIGNED NOT NULL DEFAULT 138, prefixid VARCHAR(25) NOT NULL DEFAULT '', iconid SMALLINT NOT NULL DEFAULT '0', public_preview SMALLINT NOT NULL DEFAULT '0', INDEX node_lastauthorid(lastauthorid), INDEX node_lastcontent(lastcontent), INDEX node_textcount(textcount), INDEX node_ip(ipaddress), INDEX node_pubdate(publishdate, nodeid), INDEX node_unpubdate(unpublishdate), INDEX node_parent(parentid), INDEX node_nextupdate(nextupdate), INDEX node_lastupdate(lastupdate), INDEX node_user(userid), INDEX node_oldinfo(oldcontenttypeid, oldid), INDEX node_urlident(urlident), INDEX node_sticky(sticky), INDEX node_starter(starter), INDEX node_approved(approved), INDEX node_ppreview(public_preview), INDEX node_showapproved(showapproved), INDEX node_ctypid_userid_dispo_idx(contenttypeid, userid, displayorder), INDEX node_setfor_pubdt_idx(setfor, publishdate), INDEX prefixid (prefixid, nodeid), INDEX nodeid (nodeid, contenttypeid), INDEX contenttypeid_parentid (contenttypeid, parentid), INDEX node_featured(featured), INDEX node_inlist(inlist) ) ENGINE = InnoDB

    Script: install
    Step: 2




Related Topics

Collapse

Working...
X