you need to change your thinking.  DAO is an intersection between DB
and the java code you're writing.  you should think if it as the person
coming into it after you for the first time will see it.

your method names, as the last poster said, should start to crossover
from describing the business action  performs, to which database
interaction needs to take place. ("pickProductList()" as opposed to
"pickListFromProductItemsTable()")  this is the point of DAO.

if you want another layer of abstraction, i've seen projects which
start to describe which queries or database actions will be performed
(IE "callPickListForProductItems()").  and even then contain these in a
specialized class for each database vendor, in case your application
would re-platform.

but the pattern serves you, not the other way around.  be aware of the
future and utilize as much or as little as you think you will need.