XF 1.5 Error During Install - Laragon Apache version

[arms]

Using Laragon instead of XAMPP as it has built in support for composer etc and been working great for test installs for many different packages: flarum, wordpress, laverel



But trying to install xenforo i'm getting the following error:





for ref: php-7.1.1-Win32-VC14-x86

 

[arms]

commenting out 1 line allowed it to install:

$tables['xf_user_profile'] = "
    CREATE TABLE xf_user_profile (
        user_id INT UNSIGNED NOT NULL,
         dob_day TINYINT UNSIGNED NOT NULL DEFAULT '0',
        dob_month TINYINT UNSIGNED NOT NULL DEFAULT '0',
        dob_year SMALLINT UNSIGNED NOT NULL DEFAULT '0',
         status TEXT NOT NULL,
         status_date INT UNSIGNED NOT NULL DEFAULT 0,
         status_profile_post_id INT UNSIGNED NOT NULL DEFAULT 0,
         signature TEXT NOT NULL,
         homepage TEXT NOT NULL,
         location VARCHAR(50) NOT NULL DEFAULT '',
         occupation VARCHAR(50) NOT NULL DEFAULT '',
         #following TEXT NOT NULL COMMENT 'Comma-separated integers from xf_user_follow',
         ignored TEXT NOT NULL COMMENT 'Comma-separated integers from xf_user_ignored',

Obviously not a suitable solution.

 

[SneakyDave]

Does it work if you change your commented line to

following TEXT NOT NULL,

Don't see anything wrong with that SQL at first glance

 

[arms]

Does it work if you change your commented line to


Don't see anything wrong with that SQL at first glance

Still doesn't work, and this is the standard xenforo install script, not my code
The line below is the same and works, I'm wondering if following is a reserved word or something in the newer mariadb?

 

[arms]

This says "following" is a reserved word:

https://www.drupal.org/docs/develop/coding-standards/list-of-sql-reserved-words

@Chris D

 

[arms]

    occupation VARCHAR(50) NOT NULL DEFAULT '',
         `following` TEXT NOT NULL,
        ignored TEXT NOT NULL COMMENT 'Comma-separated integers from xf_user_ignored',

worked!

 

[Chris D]

This database field hasn't changed probably for the best part of 7 years so I'm sure you can appreciate that we'd have likely seen this problem before.

I'm currently using MariaDB 10.2.5 and a clean install works fine, using Sequel Pro as a client works fine and using the mysql command line works fine:

MariaDB [(none)]> use test;
Database changed
MariaDB [test]> CREATE TABLE test_table (
    ->   following text NOT NULL
    -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.02 sec)

I'm therefore unsure why you'd have experienced problems with this but hopefully now it is installed it will be all ok from here.