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) {
;
}
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
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
FWIW :-)
Michael
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.