- Posts: 522
- Thank you received: 108
Welcome to the LimeSurvey Community Forum
Ask the community, share ideas, and connect with other LimeSurvey users!
Solution to missing database field UniqueNotification.hash in 2.59.0
- ollehar
- Topic Author
- Offline
- LimeSurvey GmbH Employee
Less
More
6 years 9 months ago #155908
by ollehar
Replied by ollehar on topic Solution to missing database field UniqueNotification.hash in 2.59.0
It's not a clean installation if the database is old.
Anyway, just create the hash column in the notifications table and you should be fine.
Anyway, just create the hash column in the notifications table and you should be fine.
The topic has been locked.
- bonanza
- Offline
- New Member
Less
More
- Posts: 6
- Thank you received: 0
6 years 9 months ago - 6 years 9 months ago #155909
by bonanza
Replied by bonanza on topic Solution to missing database field UniqueNotification.hash in 2.59.0
you're right, sorry for the confusion.
Can you give me some hints how to add the column to the table?
As my database is called 'lime', I tried:
mysql> ALTER TABLE lime_notifications ADD hash VARCHAR( 64 );
but without success.
Can you give me some hints how to add the column to the table?
As my database is called 'lime', I tried:
mysql> ALTER TABLE lime_notifications ADD hash VARCHAR( 64 );
but without success.
Last edit: 6 years 9 months ago by bonanza.
The topic has been locked.
- ollehar
- Topic Author
- Offline
- LimeSurvey GmbH Employee
Less
More
- Posts: 522
- Thank you received: 108
6 years 9 months ago #155911
by ollehar
Replied by ollehar on topic Solution to missing database field UniqueNotification.hash in 2.59.0
Sure. Which database are you using?
The topic has been locked.
- bonanza
- Offline
- New Member
Less
More
- Posts: 6
- Thank you received: 0
6 years 9 months ago #155912
by bonanza
Replied by bonanza on topic Solution to missing database field UniqueNotification.hash in 2.59.0
I'm using mysql (mysql:latest container). Thanks a lot in advance.
The topic has been locked.
- ollehar
- Topic Author
- Offline
- LimeSurvey GmbH Employee
Less
More
- Posts: 522
- Thank you received: 108
6 years 9 months ago #155913
by ollehar
Replied by ollehar on topic Solution to missing database field UniqueNotification.hash in 2.59.0
Run this (replace <prefix> with actual prefix):
alter table <prefix>_notifications add column hash varchar(64) default '';
alter table <prefix>_notifications add column hash varchar(64) default '';
The following user(s) said Thank You: bonanza
The topic has been locked.
- bonanza
- Offline
- New Member
Less
More
- Posts: 6
- Thank you received: 0
6 years 9 months ago - 6 years 9 months ago #155914
by bonanza
Replied by bonanza on topic Solution to missing database field UniqueNotification.hash in 2.59.0
Thanks a lot! Its working
A side (and maybe slightly offtopic) question: After login I now see the new logo, but the footer still says "Version 2.52+160920" which is the old version that I used. Is this maybe also because of the database which hasn't been updated/migrated when I switched to the new version? Also, when I go to the admin page and check the update settings it says the current version I can to update to using comfort-update is " 2.65.5 (170613)".
A side (and maybe slightly offtopic) question: After login I now see the new logo, but the footer still says "Version 2.52+160920" which is the old version that I used. Is this maybe also because of the database which hasn't been updated/migrated when I switched to the new version? Also, when I go to the admin page and check the update settings it says the current version I can to update to using comfort-update is " 2.65.5 (170613)".
Last edit: 6 years 9 months ago by bonanza.
The topic has been locked.
- Wins
- Offline
- New Member
Less
More
- Posts: 3
- Thank you received: 0
6 years 4 months ago #160403
by Wins
Replied by Wins on topic Solution to missing database field UniqueNotification.hash in 2.59.0
Hello,
we have the same problem after comfort updating today.
mysql> alter table lime_notifications add column hash varchar(64) default '';
ERROR 1060 (42S21): Duplicate column name 'hash'
mysql> select * from lime_notifications;
+----+
+
+
+
+
+
+
+
+
+
+
| id | entity | entity_id | title | message | status | importance | display_class | created | first_read | hash |
+----+
+
+
+
+
+
+
+
+
+
+
| 1 | user | 1 | Datenbank-Update | Die Datenbank wurde von Version 257 auf Version 260 aktualisiert. | read | 1 | default | 2016-10-25 09:13:05 | 2016-10-25 09:14:23 | NULL |
| 2 | user | 11 | Datenbank-Update | Die Datenbank wurde von Version 257 auf Version 260 aktualisiert. | read | 1 | default | 2016-10-25 09:13:05 | 2016-10-25 09:14:03 | NULL |
| 3 | user | 12 | Datenbank-Update | Die Datenbank wurde von Version 257 auf Version 260 aktualisiert. | new | 1 | default | 2016-10-25 09:13:05 | NULL | NULL |
| 4 | user | 1 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 5 | user | 11 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 6 | user | 12 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 7 | user | 16 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 8 | user | 17 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
+----+
+
+
+
+
+
+
+
+
+
+
8 rows in set (0.00 sec)
How can we fix this?
we have the same problem after comfort updating today.
mysql> alter table lime_notifications add column hash varchar(64) default '';
ERROR 1060 (42S21): Duplicate column name 'hash'
mysql> select * from lime_notifications;
+----+
+
+
+
+
+
+
+
+
+
+
| id | entity | entity_id | title | message | status | importance | display_class | created | first_read | hash |
+----+
+
+
+
+
+
+
+
+
+
+
| 1 | user | 1 | Datenbank-Update | Die Datenbank wurde von Version 257 auf Version 260 aktualisiert. | read | 1 | default | 2016-10-25 09:13:05 | 2016-10-25 09:14:23 | NULL |
| 2 | user | 11 | Datenbank-Update | Die Datenbank wurde von Version 257 auf Version 260 aktualisiert. | read | 1 | default | 2016-10-25 09:13:05 | 2016-10-25 09:14:03 | NULL |
| 3 | user | 12 | Datenbank-Update | Die Datenbank wurde von Version 257 auf Version 260 aktualisiert. | new | 1 | default | 2016-10-25 09:13:05 | NULL | NULL |
| 4 | user | 1 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 5 | user | 11 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 6 | user | 12 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 7 | user | 16 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
| 8 | user | 17 | Datenbank-Update | Die Datenbank wurde von Version 260 auf Version 263 aktualisiert. | new | 1 | default | 2017-11-08 13:18:12 | NULL | NULL |
+----+
+
+
+
+
+
+
+
+
+
+
8 rows in set (0.00 sec)
How can we fix this?
The topic has been locked.
- ollehar
- Topic Author
- Offline
- LimeSurvey GmbH Employee
Less
More
- Posts: 522
- Thank you received: 108
6 years 4 months ago #160404
by ollehar
Replied by ollehar on topic Solution to missing database field UniqueNotification.hash in 2.59.0
From which version to which version are you updating?
The topic has been locked.
- ollehar
- Topic Author
- Offline
- LimeSurvey GmbH Employee
Less
More
- Posts: 522
- Thank you received: 108
6 years 4 months ago #160405
by ollehar
Replied by ollehar on topic Solution to missing database field UniqueNotification.hash in 2.59.0
If the update is trying to create the hash column, I guess you can manually delete it before the update...
ALTER TABLE lime_notifications DROP COLUMN hash
ALTER TABLE lime_notifications DROP COLUMN hash
The topic has been locked.
- Wins
- Offline
- New Member
Less
More
- Posts: 3
- Thank you received: 0
6 years 4 months ago #160413
by Wins
Replied by Wins on topic Solution to missing database field UniqueNotification.hash in 2.59.0
Hello,
I already tried that before, didn't help. Restarted the server, tried another browser, no luck. Whatever miracle happened in the last 30 minutes, it works now.
Basically like described here: bugs.limesurvey.org/view.php?id=12732
"No, LimeSurvey still had the old database scheme cached. Most of the time this resolves itself after a few minutes but it would be nice if it did not happen in the first place."
Thanks for the help nevertheless
I already tried that before, didn't help. Restarted the server, tried another browser, no luck. Whatever miracle happened in the last 30 minutes, it works now.
Basically like described here: bugs.limesurvey.org/view.php?id=12732
"No, LimeSurvey still had the old database scheme cached. Most of the time this resolves itself after a few minutes but it would be nice if it did not happen in the first place."
Thanks for the help nevertheless
The topic has been locked.