Hi Cab, that is in fact helpful feedback. I've taken queries that we've used
for years with Millennium and Oracle, and am rewriting them for Koha and MySQL.
So far, MySQL does seem pickier. I have tried using the "EXPLAIN" command to
help identify inefficient queries, but it didn't really
Thanks for your reply, Chris. One of our team members posited that there might
be an issue---or something we can tweak--to decrease the priority of
Reports/MySQL, so that it isn’t sucking the life out of the rest of the
application. We’ll keep investigating.
Tasha Bales
Enterprise Services
Hello, we recently tried to update our development server to 21.05, and
it mostly works, but it does not like our LDAP setup, which is unchanged.
plack-error.log is filled with errors from this one:
Error while loading /etc/koha/plack.psgi: No ldapserver "hostname"
defined in KOHA_CONF:
After successful installation and configuration of ByWater Solutions
Support Plugin , when i try to run the plugin it gives an error 500.
Please help.
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:
Hi!
I'm trying to add a new facet, but it seems that the field names
available for faceted search are hardcoded in the source code in
Koha::SearchEngine::Elasticsearch->get_facetable_fields
It also seems that any changes I make via the UI in
admin/searchengine/elasticsearch/mappings.pl
are not
5 matches
Mail list logo