The issue with this is that we rely on weird string comparisons in the limit handler (e.g. we test the query finishes with for update). See the top of Oracle8iDialect.

I know in 6, we will have a proper way to fix that as we will have a proper tree of the whole query in the dialect.

For now, I would lean towards not including this and you can still use your own dialect to implement it.

And we should revisit it in ORM 6 and make the Oracle dialects not rely on string comparisons/manipulations.