>>Is there a workaround for the missing LIMIT Keyword in firebird?
>
>
> SELECT FIRST x SKIP y ...

But why not other limits?

for example:
select .... limit time 5000 ms
select .... limit read 1000 datapage
select .... limit 1000 rows

I thing if this limit can checked regularly while data retrieve/process
the database engine can except of wrong selects.

It's an easy way then break select at other thread (what planed if i
know good it).

----

select .... limit time 5000 ms
break select if time of composition too long
(for example not indexed join)

select .... limit read 1000 datapage
break select if too many datapage need to read
(for example a few record retrieving with full read against indexed)

select .... limit 1000 rows
break select if if too many result rows found
(for example join without good filter)


Why good?
- When programmer build a select, design resources too for this
statement. If something wrong the resource is less then limited.
- When programmer give a way for user (app. feasibility) for make own
'when' criterion for select, the users can define too loose condition.


eMeL