Hi Jonathan,
I have tested the solution from
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix.
A restart of the MySQL Server with a large Koha Database (several
hundred thousand biblio) or a large number of Koha Sites can take a long
time. This is mainly because the ALTER TABLE
nity.org [
> mailto:koha-devel-boun...@lists.koha-community.org
> <koha-devel-boun...@lists.koha-community.org>] *On Behalf Of *Jonathan
> Druart
> *Sent:* Friday, 21 July 2017 3:23 AM
> *To:* koha-devel@lists.koha-community.org
> *Subject:* Re: [Koha-devel] AUTO_INCREM
ha-devel-boun...@lists.koha-community.org> namens David Cook
<dc...@prosentient.com.au>
Verzonden: vrijdag 21 juli 2017 05:57
Aan: 'Jonathan Druart'; koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
Jonathan, have you thought
-boun...@lists.koha-community.org] *On Behalf Of
*Jonathan Druart
*Sent:* Friday, 21 July 2017 3:23 AM
*To:* koha-devel@lists.koha-community.org
*Subject:* Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
And see bug 18966 for a third (last!?) round. I tried to resume in the
description
...@lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Jonathan
Druart
Sent: Friday, 21 July 2017 3:23 AM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
And see bug 18966 for a third (last!?) round. I
Of Michael Hafen
Sent: Friday, 21 July 2017 1:47 AM
To: Jonathan Druart <jonathan.dru...@bugs.koha-community.org>
Cc: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
On top of that by the time you get to that error you
...@lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Jonathan
Druart
Sent: Thursday, 20 July 2017 10:10 AM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
>From Koha/Database.pm
89 RaiseEr
And see bug 18966 for a third (last!?) round. I tried to resume in the
description of the bug what has been done and what I propose to move
forward.
BE INVOLVED!
On Wed, 12 Jul 2017 at 15:11 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi devs,
>
> Please review and test
>
;
>> Ultimo, NSW 2007
>>
>> Australia
>>
>>
>>
>> Office: 02 9212 0899 <02%2092%2012%2008%2099>
>>
>> Direct: 02 8005 0595 <02%2080%2005%2005%2095>
>>
>>
>>
>> *From:* koha-devel-boun...@lists.koha-community.org [
NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899 <02%2092%2012%2008%2099>
>
> Direct: 02 8005 0595 <02%2080%2005%2005%2095>
>
>
>
> *From:* koha-devel-boun...@lists.koha-community.org [mailto:
> koha-devel-boun...@lists.koha-community.org] *On Beha
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Jonathan
Druart
Sent: Thursday, 20 July 2017 1:39 AM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
I did not get confirmation, so I am not sure you all understand how important
I did not get confirmation, so I am not sure you all understand how
important is this fix.
We are going to fix properly and globally a long standing issue, and
prevent data lost.
I *really* want to see some of you to test this trick and confirm me that
you agree on the solution and we can
...@lists.koha-community.org] On Behalf Of Katrin
Sent: Friday, 14 July 2017 7:00 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
Hi David,
the problem is not the sequence. The problem is doubled up ids between the
tables. If you try to move
Hi David,
the problem is not the sequence. The problem is doubled up ids between
the tables. If you try to move an entry with an id that already exists
in the deleted* or old* table, the data will get lost. But doubled up
ids are also likely to cause even more trouble.
Katrin
On
I’ve looked at the wiki page, but I haven’t looked at Bugzilla or the source
code. Why on Earth would we get lost data? Shouldn’t we be copying the code to
the “deleted*” tables and THEN deleting it from the main table?
In pre-5.7 versions, you could produce this same behaviour by running
It affects all versions of Koha with any versions of MySQL or MariaDB.
Last versions of Koha have been affected with bad bugs because we tried to
fix the problem at code level.
We introduced other related issues, see bug 18242 and 18651.
If you have 18242 without 18651 you may encounter problems
I only have one question about it, it only affects MySQL 5.7 and MariaDB
10.02?
Koha should not say that it works with certain version of the MySQL or
MariaDB? I been struggling a lot with issues on the DB because I'm on new
version.
Regards,
Rodrigo
On Wed, Jul 12, 2017 at 3:11 PM, Jonathan
17 matches
Mail list logo
