do we really want postgres support NOW ?
Hello again, We are a few days before a beta release of Koha 3.0 chris N. adds a lot of feature to support postgresSQL. which is undoubtfully a good feature. But do we want it now ? after rebasing this morning, all my koha setups were messed up : encoding was wrong again. Looking at last night commits, i've found a small error : $dbname instead of $db_driver in Context.pm This may have been unseen by the RM if test were not using non ascii char. The fix was trivial to do (patch sent to kados & chris) But I think we should NOT do so deep changes now. Maybe it's time for a 3.0-stable branch in git that will get only bugfixes ? -- Paul POULAIN, consultant senior BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19
Hi Paul, On 11/14/07, Paul POULAIN <paul.poulain@free.fr> wrote:
after rebasing this morning, all my koha setups were messed up : encoding was wrong again.
Not sure what happened here. My changes should have been mostly transparent to the mysql stuff. Although possibly there were issues if you use symlinks to run over your clone. Can you provide more detail/thought on what broke so that I can double check on my code changes?
Looking at last night commits, i've found a small error : $dbname instead of $db_driver in Context.pm This may have been unseen by the RM if test were not using non ascii char. The fix was trivial to do (patch sent to kados & chris)
A typo... Sorry... :-(
But I think we should NOT do so deep changes now. Maybe it's time for a 3.0-stable branch in git that will get only bugfixes ?
FWIW: I would have no problem with this as I'm not sure all the Pg stuff will be worked out in time for the 3.0 release. Regards, Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org ------------- NOTICE: The information contained in this electronic mail message is intended only for the use of the intended recipient, and may also be protected by the Electronic Communications Privacy Act, 18 USC Sections 2510-2521. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender, and delete the original message. Thank you.
El 14/11/07 05:48, Paul POULAIN escribió:
We are a few days before a beta release of Koha 3.0 chris N. adds a lot of feature to support postgresSQL. which is undoubtfully a good feature.
But do we want it now ?
Supporting PostgreSQL now seems very important right now. While Koha 3.0 introduces great new features, I think most libraries and interested people are doing well with 2.2 ATM, so maybe 3.0 can be delayed a little while in order to release it with Pg support, which will be a big breakthrough, I think. Just two cents, Jose
Hello all,
But do we want it now ?
Supporting PostgreSQL now seems very important right now. While Koha 3.0 introduces great new features, I think most libraries and interested people are doing well with 2.2 ATM, so maybe 3.0 can be delayed a little while in order to release it with Pg support, which will be a big breakthrough, I think.
Just two cents, Jose
Haven't done any devel in Koha itself, but being both a developer and a systems administrator, I've been monitoring this list (as well as the general user list) to be well informed and that I can support a library migrating from a card catalog (over 50,000 books) to Koha (I support the school in IT in general, library is just one of our projects). Introduction over, to the point. At our end, we are using 2.2.8 (recently moved over to 2.2.9) to get comfortable with the system and start the cataloging but are looking at 3.0 with much interest (not counting such upgrades always sound good to a board of directors). So in our case, zebra will be our back-end. Is there truly such a big interest in PostgreSQL over MySQL compared to Zebra over MySQL? Then again, that's only at my end... just thought I'd voice my opinion and it can be taken as just my one cent ;) BR, Andrew Séguin
participants (4)
-
Andrew Seguin -
Chris Nighswonger -
José Miguel Parrella Romero -
Paul POULAIN