Comments on: Speeding up queries by a factor of 100 or more with DB2 Text Search https://programmingzen.com/getting-started-with-db2-text-search/ Meditations on programming, startups, and technology Wed, 20 Jul 2011 16:51:44 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Antonio Cangiano https://programmingzen.com/getting-started-with-db2-text-search/#comment-24405 Wed, 20 Jul 2011 16:51:44 +0000 http://programmingzen.com/?p=1397#comment-24405 In reply to johno.

Good spotting, Johno. It was meant to be ‘%name%’ in the article from the very beginning (which was what took 25+ seconds). I fixed it now.

]]> By: duke https://programmingzen.com/getting-started-with-db2-text-search/#comment-24404 Wed, 20 Jul 2011 14:52:14 +0000 http://programmingzen.com/?p=1397#comment-24404 DB2 text search cannot distinguish between C++ and C#

Is this likely to be fixed any time?

thanks

]]> By: johno https://programmingzen.com/getting-started-with-db2-text-search/#comment-24396 Wed, 20 Jul 2011 11:12:15 +0000 http://programmingzen.com/?p=1397#comment-24396 Queries using like “name%” actually should use index on name. It’s called prefix search. And normally you would also have a limit clause there, since you really don’t need to retrieve all matches when someone queries for something general like “peter%”.

What you probably wanted to write is a query with “%name%”. It has the same semantics as CONTAINS.

]]>