> Hi
>
> We upgraded our system from 6.4 to the new 6.5 version. The set query_limit function
>is not working
> anymore in 6.5.
>
> db => set query_limit to '100';
> SET VARIABLE
> db => select * from table;
>
> statement is returning all records from the table. What's wrong here?
>
Use the
Marcus "Mike" Mascari wrote:
> What I would like to see (perhaps its possible
> right now, or a workaround is available) is a method
> for yielding an elog() message when the number of
> tuples to be returned is over a specified USER limit.
>
> [...]
>
> However, what we would like to prevent is
What I would like to see (perhaps its possible
right now, or a workaround is available) is a method
for yielding an elog() message when the number of
tuples to be returned is over a specified USER limit.
The thrust of this issue is that we are rolling out
a PostgreSQL database which is driven
Try: select * from table LIMIT 100;
> Hi
>
> We upgraded our system from 6.4 to the new 6.5 version. The set
> query_limit function is not working
> anymore in 6.5.
>
> db => set query_limit to '100';
> SET VARIABLE
> db => select * from table;
>
> statement is returning all records from the t
On Wed, 30 Jun 1999, Herbert Liechti wrote:
> We upgraded our system from 6.4 to the new 6.5 version. The set query_limit function
>is not working
> anymore in 6.5.
>
> db => set query_limit to '100';
> SET VARIABLE
> db => select * from table;
>
> statement is returning all records from the t
Hi
We upgraded our system from 6.4 to the new 6.5 version. The set query_limit function
is not working
anymore in 6.5.
db => set query_limit to '100';
SET VARIABLE
db => select * from table;
statement is returning all records from the table. What's wrong here?
Herbie
--
~
