Edson Carlos Ericksson Richter wrote:
select * from mytable where mydescription like '%something%'
For this query, the execution plan doesn't uses the index containing
mytable.mydescription, and take near to 68,09 secs (~32 times slower).
Why the "explain" says index use for first query, and a tab
Hi!
I have a 65 records table with several fields, in MaxDB 7.5.0.24 for
linux. Work pretty well.
But, if I issue:
select * from mytable where mydescription like 'something%'
the execution plan uses the index containing mytable.mydescription, and
take near to 2,07 secs. Good performance, goo
