I'll do the vote.  The patch I have will affect databases other than MySQL, so 
it wouldn't be the best to include.

Steve

From: [email protected] [mailto:[email protected]] On Behalf Of Ben Wolfe
Sent: Wednesday, May 09, 2012 11:07 AM
To: [email protected]
Subject: Re: [OPENMRS-DEV] ILIKE Ticket TRUNK-2767

Sorry about the delay.  It is not scheduled yet, and probably hasn't hit the 
lists of bugs to focus on because it has zero votes.  Click the "vote" button 
on the right-hand side to increase its visibility.

If you have a patch that doesn't change the current functionality, please apply 
it to the ticket.  That will make it 10x faster to get it applied and 
backported!

Ben
On Wed, May 9, 2012 at 10:51 AM, McKee, Steven Jay 
<[email protected]<mailto:[email protected]>> wrote:
Does anyone know if this ticket is going to be worked in the near future?  I 
know we opened this last October while upgrading to OpenMRS 1.7.  This is 
currently the only ticket keeping CHICA from using OpenMRS as is.  Currently we 
have a patch that we have to apply to fix the slow query issue before 
deployment.  Our patch removes the ilike completely and just uses a like since 
MySQL is case insensitive.  It also does an equals instead of a like when the 
"searchOnPhrase" is null to help performance.

This affects class: org.openmrs.api.db.hibernate.HibernateConceptDAO.java 
method getConcepts.

https://tickets.openmrs.org/browse/TRUNK-2767

Thanks,
Steve

________________________________
Click here to 
unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> 
from OpenMRS Developers' mailing list

________________________________
Click here to 
unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> 
from OpenMRS Developers' mailing list

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to