Hi Carlos,
We are not very far from supporting Postgresql I think.
You can find relevant bug reports linked to the umbrella bug 7365
(Koha should support PostgreSQL)
There is no active work currently done directly on that.
But refactoring and moving our code to the Koha namespace, as well as
>
> Just a quick note that string freeze will go into effect at the end of day
> 12/16/2019 for the maintenance branches.
>
> Maintenance releases scheduled for the 23rd.
>
> Translations can begin on the 17th.
>
Strings for 19.11, 19.05 and 18.11 have been updated today, last run
tomorrow.
Interesting to have this conversation come up at this time,
We've been fighting recently to maintain compatability with both MySQL and
MariaDB as in recent times they have started to diverge.
On a personal note, I don't feel agnosticism is the best route, I'd like to
see us pick a DB as a
Thanks David.
With kind regards from the Dalton McCaughey Library Team
Carlos Lopez
Dalton McCaughey Library | 29 College Crescent, Parkville, VICTORIA 3052
Ph: 03 9340 ext.1 | libr...@dml.vic.edu.au | library.dmlibrary.org.au
-Original Message-
From: dc...@prosentient.com.au
On Wed, Dec 11, 2019 at 5:53 PM Kerrie Stevens
wrote:
> We have version 18.11.11 and I’ve looked through the reports library but
> can’t see anything that looks similar to be tweaked into what I need.
>
Try this, for year 2019
SELECT month, day, suc+uns AS total, suc AS succesful, uns AS
I am expecting to see something just before this error. Maybe you did
not restart plack?
Consider jumping into IRC and catch me there, that would be easier ;)
Le mer. 18 déc. 2019 à 17:09, Tadesse, Bruck a écrit :
>
> Jonathan,
> I am not sure if I am looking in the right place and thanks for
Jonathan,
I am not sure if I am looking in the right place and thanks for your patient
with me. I opened the " intranet-error.log " log file (tail -f
intranet-error.log) in the backend and see the result below. Could this be any
helpful.
Thanks.
Bruck.-
*
[Wed
Have a look at the Koha log file, you should see the value of $value in it.
Le mer. 18 déc. 2019 à 13:23, Tadesse, Bruck a écrit :
>
> Jonathan,
>
> Thanks, the SQL query returns empty set. I have also added the debug
> statement just before the line 1627 and there is no change to the error
>
Hi fellow Koha users,
Our readers send us from time to time a 'Cart' from the online catalog to
reserve one or a few books. Is there a way to modify which fields are sent
through with this 'Cart'?
For example:
- Field 020a (ISBN): can be ommited, has no relevance for us in this case.
- Field
Jonathan,
Thanks, the SQL query returns empty set. I have also added the debug statement
just before the line 1627 and there is no change to the error message. Thinking
it is a browser cache issue, I changed computer and browser, the debug
statement didn’t bring any change to the error
Bruck,
My understanding of the error is that you have a field that is mapped
with the "authorised value" branches (that's not a real authorised
value). But at least one of those field has a value that is not a
branchcode defined in your system.
The weird thing is that, by default, only item's
Dear Karam,
Thanks, Since the update didn’t result in solving the problem, I will revert
back for now. I have taken a snapshot of the VM, so it easy to do that. I would
still appreciate any advice that would help me resolve the underlying problem
of updating the items.
Thanks,
Bruck T.
From:
Hello Bruck,
This query (UPDATE items SET homebranch='LIB', holdingbranch='LIB') ) is
very dangerous.
This will set all (homebranch and holdingbranch ) in your items table to
be LIB for all items!
if that is not what you want, then try to retrieve a backup from (
/var/spool/koha ) or
Hi All,
I have just recently upgraded to 17.05 from 16.05 and when I try to edit items
on Koha, it throws the following error "Can't call method "branchname" on an
undefined value at /usr/share/koha/lib/C4/Biblio.pm line 1627". I search the
archive online saw the advice to update the two
14 matches
Mail list logo
