- Koha-devel - lists.koha-community.org

REMINDER: Development Jitsi meeting 21 May 2025
by Paul Derscheid 20 May '25

20 May '25

Hi all, We have a Development Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_21_May_2025 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+M… Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. See you there! Paul

1 0

Re: [Koha-devel] Upgrading 17.12.00.016 failed constraint
by Michael Hafen 15 May '25

15 May '25

You could try "SET GLOBAL foreign_key_checks = 0". You could also try adding `$dbh->{AutoCommit} = 0;` to see if that will keep the foreign_key_checks setting set. That shouldn't really change anything though. I assume you are using the `koha-upgrade-schema` script to do this; that should be the way to go here. I don't know what to do beyond that. Maybe someone else on the mailing list has better ideas. On Mon, May 12, 2025 at 11:55 AM Philippe Blouin < philippe.blouin(a)inlibro.com> wrote: > Hi Michael, > > Ya, the "a lot of work" is not an option, this is an hourly-rate contract. > > I've update tons of database over that version, and this never occured. > And I've tried manually removing the constraint, and it failed on the next > one, alphabetically. > > I've tried a few hack to put more "SET foreign_key_checks = 0" everywhere, > but this clearly has no effect. > > Note: "type" is content, it's not the type of db column, but the name of > the column account_offsets.type which is an enum. > > > [image: Logo inLibro] <https://inLibro.com> Philippe Blouin > Directeur de la technologie > > T 833-INLIBRO (465-4276) <833-465-4276>, poste 230 > C philippe.blouin(a)inLibro.com > > www.inLibro.com <https://inLibro.com> > On 2025-05-12 12:40, Michael Hafen wrote: > > Yes, that update turns off the foreign key checks for the duration, but > I'm not sure that that would affect the column type, I think it only > affects column content checks. But I could be wrong. > This update does more than add the collate I think. It does check the > collate to see if the update has already been applied, but it also changes > the column data/character type from utf8-mb3 to utf8-mb4 (from 3 byte > characters to 4 byte characters) (at least I think it was utf8-mb3 before > this). > I'm surprised that there is only one error, but it may be that this is the > first table being tried. > Quick google search shows what I expected, which is a recommendation to > drop all foreign key constraints, and then add them all back once all the > alter table statements have executed. However, I'm surprised that it is > needed. I've done this same operation on several mysql databases with no > foreign key errors. The MariaDB website doesn't show any significant > changes to how that variable operates since 10.3 ( > https://mariadb.com/docs/server/ref/mdb/system-variables/foreign_key_checks/) > I expect it to just work. Makes me wonder if the database connection is > getting reset after the 'SET' statement. Maybe it needs to be 'SET GLOBAL > ...' or maybe make sure autocommit is off? > Frankly I'm at a loss. I'd hate to say 'just drop all the foreign keys > and re-create them after the update.' That seems like a lot of work; there > should be an easier way to get this to go. > > > On Mon, May 12, 2025 at 8:16 AM Philippe Blouin via Koha-devel < > koha-devel(a)lists.koha-community.org> wrote: > >> Sunny day all! >> >> First time I have this problem: I'm trying to upgrade a 17.05 to 24.11, >> but it keeps failing on constraints >> >> Upgrade to 17.12.00.015 done (Bug 20144 - Adapt DB structure to work with >> new SQL modes) >> {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change column >> 'type': used in a foreign key constraint >> 'koha_henryville/account_offsets_ibfk_t' of table >> 'koha_henryville/account_offsets' at /usr/share/perl5/DBIx/Class/Schema.pm >> line 1118. >> >> DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x5e4975bc04e8), "DBI >> Exception: DBD::mysql::db do failed: Cannot change column"...) called at >> /usr/share/perl5/DBIx/Class/Storage.pm line 113 >> >> DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::mysql=HASH(0x5e497aefac50), >> "DBI Exception: DBD::mysql::db do failed: Cannot change column"...) >> called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1623 >> DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: >> Cannot change column 'type': used i"..., DBI::db=HASH(0x5e497b75b710), >> undef) called at ./installer/data/mysql/updatedatabase.pl line 15545 >> >> This was an install on Debian 12 / Mariadb 10.11 with the koha-common >> packages, so I figured maybe some new constraints in Mariadb were in >> cause. I moved the DB to a Ubuntu 22, Mariadb 10.6 with dev install but I >> have the same problem. >> >> I've never encountered it in my upgrades up to 24.05, and there's no way >> to skip it since it's a loop through ALL the tables to add the COLLATE, >> etc... >> >> And the code starts with skipping the constraints, so I don't get it. >> >> Any suggestion? >> >> >> Best regards >> -- >> [image: Logo inLibro] <https://inLibro.com> Philippe Blouin >> Directeur de la technologie >> >> T 833-INLIBRO (465-4276) <833-465-4276>, poste 230 >> C philippe.blouin(a)inLibro.com >> >> www.inLibro.com <https://inLibro.com> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ >> > > > -- > Michael Hafen > Washington County School District Technology Department > Systems & Security Analyst > > -- Michael Hafen Washington County School District Technology Department Systems & Security Analyst

3 2

REMINDER: Development Jitsi meeting 21 May 2025
by Paul Derscheid 14 May '25

14 May '25

Hi all, We have a Development Jitsi meeting scheduled for Wednesday next week: https://wiki.koha-community.org/wiki/Development_IRC_meeting_21_May_2025 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+M… Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. See you there! Paul

1 0

Call for news - Newsletter May 2025
by Michael Kuhn 13 May '25

13 May '25

Hi I'm collecting news for the May 2025 Koha Community Newsletter. Please send anything noteworthy to: mik (at) adminkuhn (dot) ch News criteria: * Relevant news items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Upgrading 17.12.00.016 failed constraint
by Philippe Blouin 12 May '25

12 May '25

Sunny day all! First time I have this problem: I'm trying to upgrade a 17.05 to 24.11, but it keeps failing on constraints Upgrade to 17.12.00.015 done (Bug 20144 - Adapt DB structure to work with new SQL modes) {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change column 'type': used in a foreign key constraint 'koha_henryville/account_offsets_ibfk_t' of table 'koha_henryville/account_offsets' at /usr/share/perl5/DBIx/Class/Schema.pm line 1118. DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x5e4975bc04e8), "DBI Exception: DBD::mysql::db do failed: Cannot change column"...) called at /usr/share/perl5/DBIx/Class/Storage.pm line 113 DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::mysql=HASH(0x5e497aefac50), "DBI Exception: DBD::mysql::db do failed: Cannot change column"...) called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1623 DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: Cannot change column 'type': used i"..., DBI::db=HASH(0x5e497b75b710), undef) called at ./installer/data/mysql/updatedatabase.pl line 15545 This was an install on Debian 12 / Mariadb 10.11 with the koha-common packages, so I figured maybe some new constraints in Mariadb were in cause. I moved the DB to a Ubuntu 22, Mariadb 10.6 with dev install but I have the same problem. I've never encountered it in my upgrades up to 24.05, and there's no way to skip it since it's a loop through ALL the tables to add the COLLATE, etc... And the code starts with skipping the constraints, so I don't get it. Any suggestion? Best regards -- Logo inLibro <https://inLibro.com> Philippe Blouin Directeur de la technologie T 833-INLIBRO (465-4276) <tel:833-465-4276>, poste 230 C philippe.blouin(a)inLibro.com www.inLibro.com <https://inLibro.com>

2 1

Bugzilla move to new server
by Chris Cormack 06 May '25

06 May '25

Kia ora koutou As some of you are aware we are planning to move bugzilla to a new server. This is a warning that this will take place after the next major release later this month. I will send out another notice closer to the time. There will be an outage but I am not expecting it to be that long. Chris

1 0

REMINDER: Development Jitsi meeting 7 May 2025
by Paul Derscheid 06 May '25

06 May '25

Hi all, We have a Development Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_7_May_2025 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+M… Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. If you are lead or supporter of a roadmap project, we will be happy to get an update on progress. Note: Elections for the roles for 25.11 will be held at this meeting, here’s the relevant wiki page: https://wiki.koha-community.org/wiki/Roles_for_25.11. The meeting will be moderated by someone else (still waiting for confirmation) this time as I am unfortunately unavailable. Paul

1 0

Re: [Koha-devel] [Koha] Invalid value "0000-00-00 00:00:00" in field "borrowers.updated_on" with LDAP
by Michael Kuhn 05 May '25

05 May '25

Hi Chris Many thanks for your message! You wrote: > My far from optimal "workaround" (yeah... permanent workaround :) ) > for this issue was to cron a shellscript to run every minute during > library hours which does this: > > /usr/bin/mysql -u *db user* -D "*library database name*" -e "update > borrowers set updated_on = NULL where updated_on = '0000-00-00 > 00:00:00';" &>> /home/*user*/quickfix.log; > > Anything bookended by *'s is redacted. The log catches any errors or > messages. > > I keep meaning to experiment with inserting a NULL value from the xml > LDAP config, but am yet to find a quiet moment for that. Also, not > sure if it's any better a solution, since much as it pains me to run a > polling-type script every minute, it fixes the issue when it's there > but otherwise does nothing with little overhead, whereas re-inserting > a NULL value only has the benefit of being a non-polling approach. > > Anyway, that's one way to do it. I now just implemeted the command in the crontab. It's about the same idea I alread use on my Koha demo installation to prevent some wise guys to change the password of the supreuser so they have the whole installation for themselves - there I reset the password every minute to the original one every minute. As Alex Buckley pointed out in mailinglist "koha-devel" the error is probably fixed with https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36822 in Koha 24.05.06. 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 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch > On Mon, Nov 18, 2024 at 8:51 PM Michael Kuhn <mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch>> wrote: > > Hi > > In an installation of Koha 24.05.03 I am successfully authenticating > against an LDAP server which is writing the data of the authenticating > user into the Koha database. But as soon as I search for the added user > in the staff client I get the message: "500: Internal Server Error. > Month out of range." This is because table field "borrowers.updated_on" > is automatically filled with the value "0000-00-00 00:00:00". > > I am aware of bug > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31143 > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31143> (We > should attempt to fix/identify all cases where '0000-00-00' may still > remain in the database) but of course it is not possible to manually > change the value of field "borrowers.updated_on" from "0000-00-00 > 00:00:00" to NULL every time a user successfully logs into the OPAC. > > So I tried to set the value of "borrowers.updated_on" by using lines > like the following, but unfortunately they all resulted in the invalid > value "0000-00-00 00:00:00". > > <updated_on is="">NULL</updated_on> > <updated_on is="potato"></updated_on> > <updated_on is="">2024-11-18 00:00:00</updated_on> > > How can I prevent Koha filling in this invalid value when > authenticating > against LDAP and instead generate a NULL value? > > 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 · E mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> > _______________________________________________ > > Koha mailing list http://koha-community.org <http://koha-community.org> > Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha> >

2 1

REMINDER: Development Jitsi meeting 7 May 2025
by Paul Derscheid 30 Apr '25

30 Apr '25

Hi all, We have a Development Jitsi meeting scheduled for Wednesday next week: https://wiki.koha-community.org/wiki/Development_IRC_meeting_7_May_2025 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+M… Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. If you are lead or supporter of a roadmap project, we will be happy to get an update on progress. Note: I was asked to send an additional reminder a week early and this is the first time I managed to remember on time :) See you there! Paul

1 0

Koha, hackfest, bibframe, initiating discussion
by Paul Poulain 30 Apr '25

30 Apr '25

Hello, Opening the thread here, so ppl not attending the hackfest know what I plan to talk about during the hackfest. The LoC is moving to bibframe. In France, ABES seems to plan the same movement. So, I want to look after bibframe, see what people think about it, how it could be implemented in Koha... I've started a presentation, it's a 1st step to start the discussion. Feel free to take a look at it and add some comment. If you want a "modify" access, just ask me. https://docs.google.com/presentation/d/18RniwMJROfMHWy_1eeJ2zscg-qrh1NcndPJ… Very excited to see some of you in 10 days ! -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

2 2