db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From T K <sanokist...@yahoo.com>
Subject Table of 13 rows still needs an index to make it performant?
Date Tue, 08 Sep 2009 18:14:29 GMT
I have a table with a blob and 13 rows in it; in the following, please notice the execution

1) Selecting the primary key:
SELECT primkey from sometable
Query 1 of 1 elapsed time (seconds) - Total: 0.032, SQL query: 0.016, Building output: 0.016

2) Select the primary key with WHERE clause:
SELECT primkey from sometable WHERE  someString = 'someValue'
Query 1 of 1 elapsed time (seconds) - Total: 0.843, SQL query: 0.828, Building output: 0.015

3) Here's how many rows I have:
select count(*) from sometable

Does the sheer fact that the table has a blob, albeit not selected, affect query execution
THAT much? Any suggestions to improve it?


View raw message