[horde] db integrity constraint violation while turba upgrade to 4.2.0
Rene Zeipelt
zeipelt at uni-wuppertal.de
Mon Jul 14 13:40:20 UTC 2014
Am 14.07.2014 10:55, schrieb Claude Tompers:
> On 07/14/2014 10:43 AM, Rene Zeipelt wrote:
>> Hello,
>> while upgrading horde from 5.1.6 to 5.2 the turba upgrade reports the
>> db migrating error:
>>
>> [ INFO ] Migrating DB up.
>> [ INFO ] Current turba schema version: 9
>> Migrating to TurbaUpgradeCategoriesToTags (10)
>> == 10 TurbaUpgradeCategoriesToTags: migrating
>> =================================
>> == 10 TurbaUpgradeCategoriesToTags: Migrating contact categories to
>> tags. =====
>> -- select('SELECT object_uid, object_category, owner_id FROM
>> turba_objects')
>> -> 0.0006s
>> SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry
>> 'ausername' for key 'rampage_users_user_name'
>>
>> Is there a way to find the wrong data set manually?
>> The user did logins with "Ausername" and "ausername" (against a imap
>> server).
>> Thanks for help.
>> Regards Rene Zeipelt
>>
>>
> Hi Rene,
>
> I had the same problem. I solved it with
>
> UPDATE turba_objects SET owner_id=LOWER(owner_id);
>
> kind regards,
> Claude
>
>
>
Thanks to Claude for the advice, so I have some different entries for
owner_id in turba_objects and user_name (also "Ausername" here) in
rampage_users table.
After correcting it the scripts runs error free. Best Regards Rene
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5221 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20140714/dc661032/attachment.bin>
More information about the horde
mailing list