Interesting observation.

For Sybase the optimizer determines index usage when the query is run the first time. So if the first request only has a trailing '%' and the column has an index it will be used. A subsequent query with a leading '%' won't be incorrect - the optimizer detects the leading '%' and while it uses the index it will look at all the values for a match.

However, if the first query has a leading '%' then you will get a table scan each time.

I ran the following:

my $sth = $dbh->prepare("select * from market where commodity like ?")
+;

$sth->execute("SPM%");
while(my $d = $sth->fetch) {
    ;
}

$sth->execute("%XXX%");
while(my $d = $sth->fetch) {
    ;
}

[download]
The showplan output shows that the index is used, but the stats IO shows that the second execute() call does a lot more work: 
Table: market scan count 1, logical reads: (regular=111 apf=0 total=11
+1), physical reads: (regular=0 apf=0 total=0), apf IOs used=0

[download]
vs. 
Table: market scan count 1, logical reads: (regular=51889 apf=0 total=
+51889), physical reads: (regular=0 apf=0 total=0), apf IOs used=0

[download]

FWIW :-)

Michael

In reply to Re: Where the advice to use DBI bind parameters can go wrong (long) by mpeppler
in thread Where the advice to use DBI bind parameters can go wrong (long) by dws

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.