error upgrade 1.5.5 to 1.5.6

bdwmq8

When I go to my browser an click on upgrade I get the following - I have gone back to 1.5.5 which works well except for email access
anyone with any solution?
Thanks

Type: E_USER_ERROR (256)
Message: PATCH APPLY ERROR: Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1833: Cannot change column 'name': used in a foreign key constraint 'history_ibfk_1' of table 'BD_BD1.history'] in EXECUTE("ALTER TABLE session MODIFY COLUMN name VARCHAR(128) NOT NULL") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'session_client_ibfk_1'] in EXECUTE("ALTER TABLE session_client MODIFY COLUMN session_name VARCHAR(128) NOT NULL") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'history_ibfk_1'] in EXECUTE("ALTER TABLE history MODIFY COLUMN session_name VARCHAR(128) NOT NULL")
File: /home/BD/public_html/EPESI/include/patches.php
Line=35
error backtrace:
[PHP core called function]
function called: handle_epesi_error(256, "PATCH APPLY ERROR: Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1833: Cannot change column 'name': used in a foreign key constraint 'history_ibfk_1' of table 'BD_BD1.history'] in EXECUTE(\"ALTER TABLE session MODIFY COLUMN name VARCHAR(128) NOT NULL\") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'session_client_ibfk_1'] in EXECUTE(\"ALTER TABLE session_client MODIFY COLUMN session_name VARCHAR(128) NOT NULL\") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'history_ibfk_1'] in EXECUTE(\"ALTER TABLE history MODIFY COLUMN session_name VARCHAR(128) NOT NULL\") ", "/home/BD/public_html/EPESI/include/patches.php", 35, Array (true, "data/patches_log.txt", ???, Array (#3), Object (Patch), "PATCH APPLY ERROR: Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1833: Cannot change column 'name': used in a foreign key constraint 'history_ibfk_1' of table 'BD_BD1.history'] in EXECUTE(\"ALTER TABLE session MODIFY COLUMN name VARCHAR(128) NOT NULL\") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'session_client_ibfk_1'] in EXECUTE(\"ALTER TABLE session_client MODIFY COLUMN session_name VARCHAR(128) NOT NULL\") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'history_ibfk_1'] in EXECUTE(\"ALTER TABLE history MODIFY COLUMN session_name VARCHAR(128) NOT NULL\") "))

File: /home/BD/public_html/EPESI/include/patches.php
line 35
function called: trigger_error("PATCH APPLY ERROR: Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1833: Cannot change column 'name': used in a foreign key constraint 'history_ibfk_1' of table 'BD_BD1.history'] in EXECUTE(\"ALTER TABLE session MODIFY COLUMN name VARCHAR(128) NOT NULL\") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'session_client_ibfk_1'] in EXECUTE(\"ALTER TABLE session_client MODIFY COLUMN session_name VARCHAR(128) NOT NULL\") Error occured. File: /home/BD/public_html/EPESI/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: mysqlt error: [1832: Cannot change column 'session_name': used in a foreign key constraint 'history_ibfk_1'] in EXECUTE(\"ALTER TABLE history MODIFY COLUMN session_name VARCHAR(128) NOT NULL\") ", 256)

File: /home/BD/public_html/EPESI/update.php
line 2727
function called: apply_new(true)

File: /home/BD/public_html/EPESI/index.php
line 38
function called: require_once("/home/BD/public_html/EPESI/update.php")

ajb

Hi,

I don't get do you want to upgrade or downgrade? ;P
Downgrade is not supported! You can only restore a backup of files and database.

I've got similar issue and it was related to the collation of the fields. When you alter column the altered column gets the collation of the table, but it can't refer a field with the other collation. This is what happens during your upgrade.

If you can then please use the PhpMyAdmin(or any other convinient method) to check collations of the tables: session, session_client and history, then check the collations of the respective fields name, session_name.

Regards,
Adam

bdwmq8

hi Adam
Thanks for the reply - definitely trying to upgrade! When it didn't work I just went back to 1.5.5 I checked as suggested and all Collation for the tables are utf8_unicode_ci. there are some in the dbase that are latin1_swedish_ci but would a mix make a difference? not sure where to go to get the upgrade to be successful.
Thanks
Alan

jasiek

Alan,

As EPESI uses UTF-8 to store all possible characters this is the collation that you should use.
Properly setup database will use UTF-8 automatically by default, however I've seen cases where tables will use for example swedish or other.

Just change all tables to utf8_unicode_ci and you'll be fine.

bdwmq8

Hi Jasiek
I changed all the collation and retried to upgrade with the same error.
I am running 5.6.17
Reading around this I found

As of 5.6.7, the server prohibits changes to foreign key columns with the potential to cause loss of referential integrity. A workaround is to use ALTER TABLE ... DROP FOREIGN KEY before changing the column definition and ALTER TABLE ... ADD FOREIGN KEY afterward.
The release notes say this is related to http://bugs.mysql.com/bug.php?id=46599
That's fine, however...
http://dev.mysql.com/doc/refman/5.6/en/ ... -keys.html says:
Corresponding columns in the foreign key and the referenced key must have similar data types. The size and sign of integer types must be the same. The length of string types need not be the same. For nonbinary (character) string columns, the character set and collation must be the same.
Is this relevant and any suggestions?

Thanks
Alan

ajb

Just to make sure: which collation have you changed?
Table has it's own collation, but also every column.
To get current collation with sql queries:

SHOW FULL COLUMNS FROM history; // column collation

SHOW TABLE STATUS LIKE 'history'; // table collations <- this one is important

As it states in the manual, string columns don't have to be the same length, but the collation must match.
If it doesn't help, then we'll have to write a patch to drop those relations and recreate them after altering types.

bdwmq8

Hi
I went through the whole database and made sure that both column and table Collation are utf8_unicode_ci. The update attempt gives the same error as the shown below on 4th April. Looks like a patch?
Best
Alan

ajb

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

bdwmq8

Excellent - that did the trick. Working well on 1.5.6!
Thanks

japerez

Hi.

I have the same problem, but I'm using PostgreSQL. The command SHOW CREATE TABLE don't run in PostgreSQL.

I have been looking for a solutions and I don't find any. The only fix is change SHOW CREATE TABLE by pg_dump --schema-only -t tablename by this post: http://blog.endpoint.com/2009/12/mysql-and-postgres-command-equivalents.html but this don't work because this comand is a cli command.

My error is:
[quote:3fdc5yg3]Type: E_USER_ERROR (256)
Message: PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near "CREATE" LINE 1: SHOW CREATE TABLE history ^] in EXECUTE("SHOW CREATE TABLE history") Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near "CREATE" LINE 1: SHOW CREATE TABLE session_client ^] in EXECUTE("SHOW CREATE TABLE session_client") Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null
File: /var/www/epesi_bueno/include/patches.php
Line=35
error backtrace:
[PHP core called function]
function called: handle_epesi_error(256, "PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near \"CREATE\" LINE 1: SHOW CREATE TABLE history ^] in EXECUTE(\"SHOW CREATE TABLE history\") Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near \"CREATE\" LINE 1: SHOW CREATE TABLE session_client ^] in EXECUTE(\"SHOW CREATE TABLE session_client\") Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null ", "/var/www/epesi_bueno/include/patches.php", 35, Array (true, "data/patches_log.txt", ???, Array (#3), Object (Patch), "PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near \"CREATE\" LINE 1: SHOW CREATE TABLE history ^] in EXECUTE(\"SHOW CREATE TABLE history\") Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near \"CREATE\" LINE 1: SHOW CREATE TABLE session_client ^] in EXECUTE(\"SHOW CREATE TABLE session_client\") Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null "))

File: /var/www/epesi_bueno/include/patches.php
line 35
function called: trigger_error("PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near \"CREATE\" LINE 1: SHOW CREATE TABLE history ^] in EXECUTE(\"SHOW CREATE TABLE history\") Error occured. File: /var/www/epesi_bueno/libs/adodb/adodb-errorhandler.inc.php Line: 77 Message: postgres7 error: [-1: ERROR: syntax error at or near \"CREATE\" LINE 1: SHOW CREATE TABLE session_client ^] in EXECUTE(\"SHOW CREATE TABLE session_client\") Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null ", 256)

File: /var/www/epesi_bueno/update.php
line 2727
function called: apply_new(true)

File: /var/www/epesi_bueno/index.php
line 38
function called: require_once("/var/www/epesi_bueno/update.php")

[/quote:3fdc5yg3]

Could you help me??

Thanks,

PS: Sorry for my english 😛

ajb

Of course it's a MySQL version 🙂 My intention was to help BDWMQ8 🙂
Could you please paste your error with the standard version of this patch? That from the release.
I've got PostgreSQL installation and I don't have any issue with this patch. Also please post your Postgre version.

Regards,
Adam

japerez

Hi Adam.

I want to update from epesi 1.5.3 to 1.5.6.

My error is:

[quote:tgw5w252]Type: E_USER_ERROR (256)
Message: PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null
File: /var/www/epesi_bueno/include/patches.php
Line=35
error backtrace:
[PHP core called function]
function called: handle_epesi_error(256, "PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null ", "/var/www/epesi_bueno/include/patches.php", 35, Array (true, "data/patches_log.txt", ???, Array (#7), Object (Patch), "PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null "))

File: /var/www/epesi_bueno/include/patches.php
line 35
function called: trigger_error("PATCH APPLY ERROR: Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null Error occured. File: /var/www/epesi_bueno/libs/adodb/datadict/datadict-postgres.inc.php Line: 221 Message: Undefined variable: set_null ", 256)

File: /var/www/epesi_bueno/update.php
line 2727
function called: apply_new(true)

File: /var/www/epesi_bueno/index.php
line 38
function called: require_once("/var/www/epesi_bueno/update.php")[/quote:tgw5w252]

My PostgreSQL is:

psql (PostgreSQL) 9.1.11

Regards,

ajb

It's a different error, related to adodb abstraction layer. It seems that it has a bug.
This patch should fix it. [attachment=0:3p4296hl]patch.zip[/attachment:3p4296hl]
And of course don't use that mysql version above 🙂 Just extract release package, extract that patch, and try to upgrade.

japerez

Thanks a lot! Adam.

All correct!

Regards,

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge