[Akonadi] [Bug 331867] mysql: column 'name' can not be null when migrating PartTable

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=331867

Daniel Vrátil <dvratil at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
   Version Fixed In|                            |1.12.2
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/akon
                   |                            |adi/4ca8b846baaad48ebbd723f
                   |                            |6411f9571a3b0f5ad

--- Comment #23 from Daniel Vrátil <dvratil at redhat.com> ---
Git commit 4ca8b846baaad48ebbd723f6411f9571a3b0f5ad by Dan Vrátil.
Committed on 22/04/2014 at 09:28.
Pushed by dvratil into branch '1.12'.

Remove the invalid GID part from PartTable before starting PartTable migration

More people than we expected have invalid 'GID' part in their PartTable,
which breaks migration to schema 25, because it expects all part types
to have a valid name.

To work around this fact, we DELETE all parts with name 'GID' from PartTable
before starting the actual migration. This will not fix the migration for
people with other invalid parts, but I haven't heard of any such. To make
this completely bullet-proof, we would need to iterate through all entries,
which would be massively slower than current INSERT INTO ... SELECT FROM
approach.

Distributions, this is a good choice for backporting into 1.12.1 ;-)
FIXED-IN: 1.12.2

M  +9    -0    server/src/storage/dbupdater.cpp

http://commits.kde.org/akonadi/4ca8b846baaad48ebbd723f6411f9571a3b0f5ad

-- 
You are receiving this mail because:
You are the assignee for the bug.