Forum

SQL Error in log af...
 
Notifications
Retirer tout

SQL Error in log after updating to 5.4.4

3 Posts
2 Utilisateurs
0 Reactions
2,439 Vu
(@maged-mostafa)
Posts: 16
Active Member
Début du sujet
 
[#3582]

Hi,
I upgraded from 5.3.5 to 5.4.4 and found the following SQL error in the log. Please advise about it.

2016-08-18 14:54:17.765 ===== TRACE ===== =====================================
2016-08-18 14:54:17.765 ===== TRACE =====
2016-08-18 14:54:17.765 ===== TRACE ===== VERSION V5.4.4
2016-08-18 14:54:17.765 ===== TRACE =====
2016-08-18 14:54:17.770 ===== TRACE ===== Table "cronexecution" created.
2016-08-18 14:54:17.771 ** ERROR ** Exception-[42601] SQLSTATE[42601]: Syntax error: 7 ERROR: syntax error at or near "TO"
LINE 1: ALTER TABLE action RENAME COLUMN TO isPrivate;
^
2016-08-18 14:54:17.771 ** ERROR ** For query : ALTER TABLE action RENAME COLUMN TO isPrivate;
2016-08-18 14:54:17.771 ** ERROR ** Strack trace :
2016-08-18 14:54:17.771 ** ERROR ** #0 Sql->query called at [/var/www/html/projeqtor/db/maintenanceFunctions.php:71]
2016-08-18 14:54:17.771 ** ERROR ** #1 runScript called at [/var/www/html/projeqtor/db/maintenance.php:99]
2016-08-18 14:54:17.771 ** ERROR ** #2 include called at [/var/www/html/projeqtor/tool/loginCheck.php:121]
2016-08-18 14:54:17.771 ===== TRACE =====
2016-08-18 14:54:17.771 ===== TRACE ===== Error # 1 => SQL error while executing maintenance query for version V5.4.4 (see above message)
2016-08-18 14:54:17.771 ===== TRACE =====
2016-08-18 14:54:17.771 ===== TRACE ===== *************************************************
2016-08-18 14:54:17.771 ===== TRACE =====
2016-08-18 14:54:17.771 ===== TRACE =====
2016-08-18 14:54:17.771 ===== TRACE ===== DATABASE UPDATED
2016-08-18 14:54:17.771 ===== TRACE ===== WITH 1 ERROR
2016-08-18 14:54:17.771 ===== TRACE =====
2016-08-18 14:54:17.871 ===== TRACE ===== =====================================
2016-08-18 14:54:17.871 ===== TRACE =====
2016-08-18 14:54:17.871 ===== TRACE ===== 1 ERRORS DURING UPDATE TO VERSION V5.4.4
2016-08-18 14:54:17.871 ===== TRACE =====
2016-08-18 14:54:17.871 ===== TRACE ===== =====================================


 
Posté : 18 Août PM 17:088
(@babynus)
Posts: 14952
Membre Admin
 

Hi,
This is not an issue if you migrate from 5.3.x to 5.4.4.
The erroneous command (in postgresql) is only to adapt db for those who migrated from 5.3.x to 5.4.0 and then to 5.4.4.
This will be fixed on 5.4.5, but there should not be issues due to this failed migration command.


 
Posté : 18 Août PM 17:088
(@maged-mostafa)
Posts: 16
Active Member
Début du sujet
 

Thanks for the clarification 🙂 and the suuuuuuuper fast feedback :woohoo:


 
Posté : 18 Août PM 18:088
Share:
Retour en haut