Thanks Jonathan! On Mon, Sep 25, 2017 at 11:17 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:

Awesome, thanks Jonathan!

El lun., 25 sept. 2017 a las 14:43, Jonathan Druart (< jonathan.druart@bugs.koha-community.org>) escribió:

...

Hello librarians and developers,

The what's on in koha-devel #15 is available on the Koha website: https://koha-community.org/whats-on-in-koha-devel-15

Regards, Jonathan _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha

-- Regards, Amit Gupta

Michael, 1,2 - yes it is only for data that are moved from one table to the others. The list is on the wiki page 3 - You MUST update if you use one of the versions that are listed, the code is buggy (behaviors depending on the version are listed on the wiki page) and you may loose circulation history. 4 - I am not in favor of offering a generic way to fix the corrupted data for now: we did not receive enough feedback to know how the data are wrong, and I do not think there is only 1 way to fix them. I think people will have to dig into the DB to know how data are linked (for instance see bug 19016 comment 13 for the problem with accountlines.issue_id). Cheers, Jonathan On Mon, 25 Sep 2017 at 15:36 Michael Kuhn <mik@adminkuhn.ch> wrote:

Hi Jonathan

...

The what's on in koha-devel #15 is available on the Koha website: https://koha-community.org/whats-on-in-koha-devel-15

Thanks for the update! In the section about corrupted data you wrote:

...

The last month we communicate about a bug in previous Koha versions that can lead to corrupted data. Worst, some attempts to fix this problem have introduced critical behaviors. So, this is my last call. If you are using one of these versions:

16.11.07, 16.11.08, 16.11.09 16.05.12, 16.05.13, 16.05.14 17.05.00, 17.05.01

You must upgrade as soon as possible. To avoid corrupted data, you must set the DBMS auto increment fix up correctly at DBMS configuration.

Am I correct with the following statements?

1. This problem is only relevant for libraries that are actually using the circulation module (or want to do so in the future) because it is only about corrupted circulation data in tables: borrowers, biblio, items, issues, reserves

2. The update (and as well the solution described in https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix) will only prevent corrupted data in the future, but is not fixing data that is already corrupt

3. Instead of an update (which is sometimes more difficult) it is possible to just follow the steps described in https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix

4. So far there is no approach as how to correct corrupted data (as I see the propsed script in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19016 has still to be written and is however not part of any Koha version or revision yet)

Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 <+41%2061%20261%2055%2061> · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha