Summary | Errors during Schema-Upgrade |
Queue | Turba |
Queue Version | 4.2.0 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | nschmidt (at) df (dot) eu |
Created | 08/04/2014 (3988 days ago) |
Due | |
Updated | 08/11/2014 (3981 days ago) |
Assigned | |
Resolved | 08/11/2014 (3981 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Not A Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Errors during Schema-Upgrade
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
database schema for turba i see (via horde debug log) many many sql
calls like this
[horde] SQL (0.0006s) SELECT * FROM turba_sharesng WHERE
share_name = 'EMAIL@ADDRESS' [pid 26086 on line 208 of
"/var/www/html/live/horde/pear/lib/php/Horde/Db/Adapter/Pdo/Base.php"]
but the problem is, i got errors because of duplicate entry. so i had
to dig this down, and i found that this upgradequery seems to be false ?
table "turba_sharesng" looks like this
select share_id,share_name,share_owner from turba_sharesng;
+----------+-------------------------+------------------+
| share_id | share_name | share_owner |
+----------+-------------------------+------------------+
| 1 | u9OhbsL8999OCXSF3OHCC2A | email@adress |
| 2 | 8fYeNUlCcOxOCXmlswVXnfA | email2@adresse |
+----------+-------------------------+------------------+
so the right query seems to be "SELECT * FROM turba_sharesng WHERE
share_owner...", because ob share_name only has a hash stored and not
emailaddresses ?