Welcome to Geeklog, Anonymous Tuesday, December 05 2023 @ 12:15 am EST
Geeklog Forums
Upgrade 10.3.9sr2 to 10.3.10rc4 error: 1060: Duplicate column name 'lft'
jimphelps
Anonymous

When I get to step 2 (click on next) in the upgrade script, I get the following error:
1060: Duplicate column name 'lft'
I am running 10.3.9sr2 with file management plugin (version 1.3) and menu plugin (disabled, 1.6.1) and statics pages (1.4.1).
I've dug through my libcommon.php and config.php and I can't find anything.
Any ideas?
- Jim
1060: Duplicate column name 'lft'
I am running 10.3.9sr2 with file management plugin (version 1.3) and menu plugin (disabled, 1.6.1) and statics pages (1.4.1).
I've dug through my libcommon.php and config.php and I can't find anything.
Any ideas?
- Jim
10
6
Quote
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Sounds like you've been running the upgrade on the database before. 'lft' is a new field in the comments table that has only been introduced in 1.3.10.
Restore your backup and try again.
bye, Dirk
Restore your backup and try again.
bye, Dirk
7
9
Quote
DeCEiVeR
Anonymous
I just upgraded and everything was a success but now when I go to my site I get an SQL error, in my log i get ..
Wed Nov 24 16:28:03 2004 - 1054: Unknown column 'STORY_ARCHIVE_ON_EXPIRE' in 'where clause'. SQL in question: SELECT sid,tid,title,expire,statuscode FROM gl_stories WHERE (expire
This has got to be a simple file missing or something, anyone help?
TIA..
Wed Nov 24 16:28:03 2004 - 1054: Unknown column 'STORY_ARCHIVE_ON_EXPIRE' in 'where clause'. SQL in question: SELECT sid,tid,title,expire,statuscode FROM gl_stories WHERE (expire
This has got to be a simple file missing or something, anyone help?
TIA..
9
7
Quote
DeCEiVeR
Anonymous
Quote by Dirk: Make sure you've updated your config.php. STORY_ARCHIVE_ON_EXPIRE is defined as a constant there.
bye, Dirk
bye, Dirk
1 last problem I have, and I think I'm good to go.. on the comments for stories, i get the error:
1044: Access denied for user: 'my UIDr@.%' to database 'myDB'. SQL in question: LOCK TABLES gl_comments WRITE
i've talked to my hosting company and they said everything was fine, this only happened after I upgraded from 1.3.9 to 1.3.10. Checked my comment.php file and that is the correct one.
Any idea's dirk?
10
7
Quote
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Quote by DeCEiVeR: 1044: Access denied for user: 'my UIDr@.%' to database 'myDB'. SQL in question: LOCK TABLES gl_comments WRITE
If your site is running on MySQL 4.x check with your hosting service that the database user has permissions to do table locking. IIRC, this was introduced as a new permission in MySQL 4.0.
bye, Dirk
6
7
Quote
DeCEiVeR
Anonymous
Quote by Dirk:
If your site is running on MySQL 4.x check with your hosting service that the database user has permissions to do table locking. IIRC, this was introduced as a new permission in MySQL 4.0.
bye, Dirk
Quote by DeCEiVeR: 1044: Access denied for user: 'my UIDr@.%' to database 'myDB'. SQL in question: LOCK TABLES gl_comments WRITE
If your site is running on MySQL 4.x check with your hosting service that the database user has permissions to do table locking. IIRC, this was introduced as a new permission in MySQL 4.0.
bye, Dirk
My hosting service (godaddy) said they can't grant me those permissions because it is a global flag. Why would comments in 1.3.9 work but fail in version 1.3.10rc3?
jeez, this sux if I've lost my comment function.
9
10
Quote
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Quote by DeCEiVeR: Why would comments in 1.3.9 work but fail in version 1.3.10rc3?
Because the comment code in 1.3.10 has undergone major changes.
Quote by DeCEiVeR: My hosting service (godaddy) said they can't grant me those permissions because it is a global flag.
Hmm. To my knowledge, this is just another permission, just like the one to create tables, insert records, etc:
Quote by MySQL manual: As of MySQL 4.0.2, to use LOCK TABLES you must have the LOCK TABLES privilege and a SELECT privilege for the involved tables. In MySQL 3.23, you must have SELECT, INSERT, DELETE, and UPDATE privileges for the tables.
(from the MySQL Manual)
bye, Dirk
7
8
Quote
GiAnGy
Anonymous
I have upgraded 1.3.10rc2 to 1.3.10 but I have the same error.
Why? 1060: Duplicate column name 'lft'
Regards
Why? 1060: Duplicate column name 'lft'
Regards
10
10
Quote
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Quote by GiAnGy: I have upgraded 1.3.10rc2 to 1.3.10 but I have the same error.
Did you try to upgrade the database again? That's not necessary - all the Release Candidates and the final version use the same database scheme.
bye, Dirk
10
9
Quote
GiAnGy
Anonymous
Ah okey,thanks Dirk!
8
7
Quote
horseflesh
Anonymous
The LOCK TABLES bit should be a FAQ.
Luckily I came here first when I ran into it after upgrading to 1.3.10.
I am running MySQL 4 and it does look like LOCK TABLES is a global priv. I'm no pro though, I use a mysql admin front end, but that's what it looks like.

I am running MySQL 4 and it does look like LOCK TABLES is a global priv. I'm no pro though, I use a mysql admin front end, but that's what it looks like.
7
10
Quote
Ghost
Anonymous
The following should fix it, for those who have access to grant privileges:
grant lock tables on geeklog.* to 'login'@'host' identified by 'password';
grant lock tables on geeklog.* to 'login'@'host' identified by 'password';
6
7
Quote
All times are EST. The time is now 12:15 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content