Re: Limit vs setMaxRows issue
| От | Marc Herbert |
|---|---|
| Тема | Re: Limit vs setMaxRows issue |
| Дата | |
| Msg-id | khjirm53k3c.fsf@meije.emic.fr обсуждение |
| Ответ на | Limit vs setMaxRows issue (Sebastiaan van Erk <sebster@sebster.com>) |
| Ответы |
Re: Limit vs setMaxRows issue
|
| Список | pgsql-jdbc |
Oliver Jowett <oliver@opencloud.com> writes:
> It's not a bug. setMaxRows() is essentially a hint, there's certainly
> no requirement that the driver will go off and add LIMIT clauses to
> your query,
My reading of the JDBC javadoc and my excessive "pickiness" do not
agree with the word "hint"
/**
* Sets the limit for the maximum number of rows that any
* <code>ResultSet</code> object can contain to the given number.
* If the limit is exceeded, the excess
* rows are silently dropped.
OK nothing ever tells you that the server has to behave optimally and
never compute anything useless. However in this case you know _for
sure_ that additional rows will be useless.
В списке pgsql-jdbc по дате отправления: