I agree it is better to have the staff learn to use '%' in the query if they want. Mason, I'd suggest for the library that wants this, to use a bit of javascript to append it to the query. As Joe mentioned, and I mentioned in the bugzilla enhancement record, a 'starts with' just doesn't make sense for most libraries around these parts; the more often desired behavior is to be able to type in the _last_ few digits of the card number.
So it shouldn't default to a cardnumber starts-with anyway, imo. Maybe a better solution is to add a 'staff user js' syspref, which would make it easier to attach a local function to alter the patron search queries? Ryan On Fri, Jul 25, 2008 at 2:57 AM, paul POULAIN <[EMAIL PROTECTED]> wrote: > Mason James a écrit : > > Some good points raised here, especially Joe's point re: performance > > > > So, its good for Koha to attempt to return some results - if no > > results are returned... > > But there needs to be a LIMIT (10 or 100?) on those results, so staff > > dont accidentlly cause runaway SQL queries. > > > Please note that the SQL "LIMIT" pragma is mySQL specific. So it must be > avoided. > > my 2cts > > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > NOUVEAU TELEPHONE : 04 91 81 35 08 > > _______________________________________________ > Koha-patches mailing list > [email protected] > http://lists.koha.org/mailman/listinfo/koha-patches > -- Ryan Higgins LibLime * Open-Source Solutions for Libraries Featuring KohaZOOM ILS 888-564-2457 x704
_______________________________________________ Koha-patches mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-patches
