Re: [sqlite] Optimising usage of LIKE

By "version" I meant "implementation". On Mon, May 3, 2010 at 7:25 AM, Tim Romano wrote: > Which version of SQLite are you using? If LIKE has been overridden in the > implementation you're using, it won't have the advantage of an index > whatever the collation, in which

Re: [sqlite] Optimising usage of LIKE

Which version of SQLite are you using? If LIKE has been overridden in the implementation you're using, it won't have the advantage of an index whatever the collation, in which case you might consider GLOB though it is case-sensitive. Regards Tim Romano

Re: [sqlite] Optimising usage of LIKE

Subject: Re: [sqlite] Optimising usage of LIKE Simon's answer is probably best -- without any benchmarks it makes the most sense. You've got at least two solutions that don't require changing your data: SELECT x FROM userTable WHERE upper(name) = upper('name'); SELECT x FROM userTable WHERE

Re: [sqlite] Optimising usage of LIKE

Northrop Grumman Mission Systems From: sqlite-users-boun...@sqlite.org on behalf of Simon Slavin Sent: Mon 5/3/2010 5:33 AM To: i...@omroth.com; General Discussion of SQLite Database Subject: Re: [sqlite] Optimising usage of LIKE On 3 May 2010, at 9:53am

Re: [sqlite] Optimising usage of LIKE

On 3 May 2010, at 9:53am, Ian Hardingham wrote: > For various embarrassing reasons, I'm using: > > SELECT x FROM userTable WHERE name LIKE 'name' > > To look up entries in my account table. Basically, the scripting > language I'm using which hooks into SQLite is a bit case-agnostic. > >