New Feature: Improved Z39.50 Client
Hi all, Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
On Thu, Nov 02, 2006 at 07:39:49PM -0800, Joshua Ferraro said:
Hi all,
Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client.
Can we get the fixes for mysql 5 in there as well. They are small and harmless, no changes of the database, just a change in the koha.msyql. And a couple of edits in Search.pm and SearchMARC.pm If people are happy ill commit the fixes Chris -- Chris Cormack Programmer 027 4500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
On Fri, Nov 03, 2006 at 04:41:33PM +1300, Chris Cormack wrote:
On Thu, Nov 02, 2006 at 07:39:49PM -0800, Joshua Ferraro said:
Hi all,
Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client.
Can we get the fixes for mysql 5 in there as well. They are small and harmless, no changes of the database, just a change in the koha.msyql. And a couple of edits in Search.pm and SearchMARC.pm
If people are happy ill commit the fixes If they are tested and known to work I'm all for it.
Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
Chris Cormack wrote:
On Thu, Nov 02, 2006 at 07:39:49PM -0800, Joshua Ferraro said:
Hi all,
Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client.
Can we get the fixes for mysql 5 in there as well. They are small and harmless, no changes of the database, just a change in the koha.msyql. And a couple of edits in Search.pm and SearchMARC.pm
If people are happy ill commit the fixes
Chris
I'd certainly be happy if the changes are as you say small and harmless, but there has been an opinion put out on the koha list based on http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1089 that major changes are needed for mysql5 support. To my mind there are two ways you could read the (non)resolution of that bug report. One is that there never was a problem in the areas the submitter was talking about, and he was fixing things that weren't broken. The other is that there are complex and not understood problems with koha-2.2 and mysql5 and it's in the too hard basket, unless extensive work and testing is done. I suspect the (2.2) release manager is in the latter camp as this bug report is referenced in the release notes of 2.2.6. It's certainly a good thing to have a warning in the 2.2.6 release mentioning mysql5 incompatibility. However, I think that bug report is not a good description the incompatibility. My own experience has been that I have installed Koha 2.2.5 with mysql5, and it is (mostly) working, but I haven't tested it extensively enough to be sure. What doesn't work (barcode printing) is I think a problem with the perl modules I have installed rather than the db. Cheers, Alex PS. Update on Debian packaging: I haven't done much, but I had trouble when trying to upgrade my 2.2.5 install to 2.2.6. The upgrade script complained of missing perl modules even after I loaded the modules through CPAN. I need to try a fresh install.
Alex King a écrit :
If people are happy ill commit the fixes
I'm 99% sure there are others SQL modifs to do, see below. That's why I won't say in 2.2.7 "we are mySQL 5.0 compliant", otherwise we will be overwhelmed by new bug reports. koha 2.2 is now stable enough, I thinks it's a very bad idea to reintroduce unstability.
I suspect the (2.2) release manager is in the latter camp as this bug report is referenced in the release notes of 2.2.6.
You are right here : our experience shows that many SQL statements are no more working properly with mySQL5 (summary : it's outdated way to do SQL joins : using where instead of LEFT JOIN). So the problem is not so easy to fix, because we can't say "2.2.x is only mySQL5 compatible, and rewritting queries is not so easy. Most (all?) distros are provided with mySQL4 as well as mySQL5, so that's not a major problem I think. In rel_3_0, toins is working hard to achieve mySQL5 compatibility, and it's not a small task because it requires many many testings. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Paul POULAIN escribió:
Most (all?) distros are provided with mySQL4 as well as mySQL5, so that's not a major problem I think.
Debian 4.0 (codename "Etch", ETA December 2006) doesn't provide MySQL 4.0 or 4.1, just a 5.0 server, and actually it might be released with a 5.1 server. Chances are you won't see MySQL 4.x officially supported in any of the next Debian releases. I had a hard time trying to setup MySQL 4.1 in an Etch box, and even after I made it, I felt uncomfortable about having MySQL outside my packaging system, so I had to fall back to Debian 3.1 which only provides MySQL 4.1, but also provides less packaged Perl modules; for example some modules under the MARC namespace are packaged in Etch but not in Sarge. I think Alex King pointed out in previous messages and threads that the Debian packaging would suffer a lot from this. This also affects Ubuntu, since they don't provide MySQL 4 since Dapper, and other Debian derivatives, including local developments we're working out in Venezuela. However I understand that it's not responsible to ship 2.2 versions of Koha with faulty or sloppy MySQL 5 support.
In rel_3_0, toins is working hard to achieve mySQL5 compatibility, and it's not a small task because it requires many many testings.
Given my previous opinions, I do consider it very important to improve (and maybe unofficially backport) MySQL 5 support in 3.0 releases of Koha. If you are going to release test packages of Koha with MySQL 5 support, please let me know so I can test it and provide some feedback. I'm sorry I can't offer my help as a DBA, since my DB skills are quite poor. I can actually help with Debian packaging if someone needs any help on that. Jose -- José M. Parrella -> Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela -> ucvlug.info
José Parrella wrote:
Paul POULAIN escribió:
Most (all?) distros are provided with mySQL4 as well as mySQL5, so that's not a major problem I think.
Debian 4.0 (codename "Etch", ETA December 2006) doesn't provide MySQL 4.0 or 4.1, just a 5.0 server, and actually it might be released with a 5.1 server. Chances are you won't see MySQL 4.x officially supported in any of the next Debian releases.
I had a hard time trying to setup MySQL 4.1 in an Etch box, and even after I made it, I felt uncomfortable about having MySQL outside my packaging system, so I had to fall back to Debian 3.1 which only provides MySQL 4.1, but also provides less packaged Perl modules; for example some modules under the MARC namespace are packaged in Etch but not in Sarge.
[snip]
Jose
FWIIW, you can "pin" versions using /etc/apt/preferences so you could pin MySQL to 4.* with a more advanced Debian system. You can also downgrade a MySQL 5.* installation to 4.*, but that might be tough because of dependencies... it is probably better to install Debian testing/Etch without MySQL, pin MySQL to 4.*, and then install MySQL (which will install 4.x since it is pinned). This is theoretical, I have not done this specifically with MySQL. YMMV. gvb
Jerry Van Baren escribió:
FWIIW, you can "pin" versions using /etc/apt/preferences so you could pin MySQL to 4.* with a more advanced Debian system. You can also downgrade a MySQL 5.* installation to 4.*, but that might be tough because of dependencies... it is probably better to install Debian testing/Etch without MySQL, pin MySQL to 4.*, and then install MySQL (which will install 4.x since it is pinned).
Sure. However the dependencies on libmysqlclient varies, and DBD::MySQL and other already-packaged modules which depend on libmysqlclient might need to be purged and compiled using dh-make-perl or any other helper, or just installed manually. I planned to recompile Sarge's source package under Etch; I guess that's the nicest way. Of course it's possible to have Koha in Etch (I had it, just decided to fallback to Sarge) it's just quite more complicate to achieve, a little bit unmanageable and currently highly complex to do by means of an official Debian package. Jose -- José M. Parrella -> Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela -> ucvlug.info
On Fri, Nov 03, 2006 at 09:22:58AM +0100, Paul POULAIN wrote:
Alex King a écrit :
If people are happy ill commit the fixes
I'm 99% sure there are others SQL modifs to do, see below. That's why I won't say in 2.2.7 "we are mySQL 5.0 compliant", otherwise we will be overwhelmed by new bug reports. koha 2.2 is now stable enough, I thinks it's a very bad idea to reintroduce unstability. Except that I think Chris said earlier in this thread that one if his clients has been running on MySQL 5 for a while now ... maybe Chris can clarify what the needed changes were and whether it's safe to apply them for 2.2.7.
Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
On Mon, 2006-11-06 at 06:01 -0800, Joshua Ferraro wrote:
On Fri, Nov 03, 2006 at 09:22:58AM +0100, Paul POULAIN wrote:
Alex King a écrit :
If people are happy ill commit the fixes
I'm 99% sure there are others SQL modifs to do, see below. That's why I won't say in 2.2.7 "we are mySQL 5.0 compliant", otherwise we will be overwhelmed by new bug reports. koha 2.2 is now stable enough, I thinks it's a very bad idea to reintroduce unstability. Except that I think Chris said earlier in this thread that one if his clients has been running on MySQL 5 for a while now ... maybe Chris can clarify what the needed changes were and whether it's safe to apply them for 2.2.7.
Cheers,
I'll second the idea of going to Chris for a MySQL 5 patch rather than going with the patch that's in bugzilla. I posted the patch that's in bugzilla, and I will be the first to say it shouldn't be applied to any version of Koha. I have made other customizations for my employer, and some of those other mod's might have snuck into the patch.
Joshua Ferraro a écrit :
Hi all,
Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client.
Great news. I agree for 2.2.7, even if I can't build the release next week. But you can be sure i'll release it this month ! -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
participants (7)
-
Alex King -
Chris Cormack -
Jerry Van Baren -
Joshua Ferraro -
José Parrella -
Michael Hafen -
Paul POULAIN