Re: experience sharing: select query returns more records than necessary

Поиск
Список
Период
Сортировка
От Dave Cramer
Тема Re: experience sharing: select query returns more records than necessary
Дата
Msg-id 491f66a50901200756w3463c85ak2e99fb8ba08f2ad@mail.gmail.com
обсуждение исходный текст
Ответ на Re: experience sharing: select query returns more records than necessary  (Kent Tong <kent@cpttm.org.mo>)
Список pgsql-jdbc


On Tue, Jan 20, 2009 at 9:43 AM, Kent Tong <kent@cpttm.org.mo> wrote:



Oliver Jowett wrote:
>
> Dave Cramer wrote:
> Though, I would suggest that if you really only care about the first 50
> results, then put a LIMIT 50 in your query! The query planner may come
> up with a better plan if you do that, too ..
>
> If you want to "stream" the whole resultset, then fetchsize is certainly
> the way to do it.
>

Yeah, I was actually settling on "LIMIT 50" before coming across
setFetchSize().
However, the support for LIMIT varies from one DBMS to another. To keep
the code as portable as possible, I decided to go with setFetchSize().

Kent,

Check the difference in the plans. Using limit can invoke an index that might not otherwise be used. It can make orders of magnitude differences in these kinds of queries.

Dave

В списке pgsql-jdbc по дате отправления:

Предыдущее
От: uprooter
Дата:
Сообщение: Re: JDBC exception, incompatible types in simple stored procedure.
Следующее
От: "Hartmann, Christian (externer Mitarbeiter)"
Дата:
Сообщение: java.sql.Statement generates java.lang.OutOfMemoryError in big tabe