<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 12088 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 195, Issue 17<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br>    koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br>    koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br>    koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br>   1. Koha Community Newsletter: February 2022 (Koha Newsletter)<br>   2. Why is "branchcode" nullable for "reserves" table?<br>      (dcook@prosentient.com.au)<br>   3. Koha releases are available 🎁 (Mason James)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 27 Feb 2022 21:04:08 +0100<br>From: Koha Newsletter <kohanews@gmail.com><br>To: koha <koha@lists.katipo.co.nz>,  koha-devel<br>    <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Koha Community Newsletter: February 2022<br>Message-ID:<br>    <CAEqgz_k3-H554q16rmED7G=oinMU3j+-Gw8988qVcdM7BZ7S3g@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>The Koha Community Newsletter for february 2022 is here:<br><br>https://koha-community.org/koha-community-newsletter-february-2022/<br><br>Many thanks to everyone who submitted articles and news to this newsletter!<br><br>Please feel free to email me with any corrections or suggestions.<br>--<br>Michael Kuhn<br>Editor, Koha Community Newsletter<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220227/c3bae5ec/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 28 Feb 2022 13:36:12 +1100<br>From: <dcook@prosentient.com.au><br>To: "'Koha Devel'" <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Why is "branchcode" nullable for "reserves"<br>    table?<br>Message-ID: <06b301d82c4b$fa5eb630$ef1c2290$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>Does anyone know why "branchcode" is nullable for the "reserves" table?<br><br> <br><br>I'm occasionally finding I have reserves with a null branchcode, and it<br>causes all kinds of problems.<br><br> <br><br>Unfortunately, I can't figure out how these reserves are being created, as<br>the UI should be preventing this from happening. I've looked at the logs and<br>tried to reproduce the problem myself and can't do it. But the action_logs<br>and the database itself confirms that there are reserves being created with<br>null branchcodes at times.<br><br> <br><br>If the database had branchcode as a NOT NULL column, we wouldn't have this<br>problem. So I'm curious why we haven't done that. thoughts anyone?<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220228/5343bca5/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 28 Feb 2022 17:17:55 +1300<br>From: Mason James <mtj@kohaaloha.com><br>To: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz>, Koha Devel<br>    <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Koha releases are available 🎁<br>Message-ID: <136fee14-3afd-7e69-6a30-d2e586bb6b93@kohaaloha.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>kia ora community,<br><br>the latest Koha packages and tarballs are ready<br><br>release notes are here...<br>   https://koha-community.org/koha-21-11-03-released<br>   https://koha-community.org/koha-21-05-11-released<br>   https://koha-community.org/koha-20-11-15-released<br>   https://koha-community.org/koha-19-11-26-released<br><br><br>cheers, Mason<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 195, Issue 17<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>