Possible solution can be to drop the "sqlHandlerSupportsMaxNumber" condition and extend the while a little in all the readNodes methods:
Anothe rpossible soilution (maybe a betetr one) which I though uip was to make "sqlHandlerSupportsMaxNumber" dependent on the Query.
Rather than have the handler always return 'true' or 'false', it might return true depending on whether it could incorporate max/offset in a query.
I prefer to go for the hack i've proposed for now, 'cause the solution you mention gonna need an interface change on the BasicQuery, that's quite a change ...
The point here is that while you can deal with 'max' not being supported in the way you propose, it is very hard to do the same for 'offset'.
Offset is not supported by the informixSQLHandler and there's also no SQL syntax for informix to perfom an "offset", so this will be taken care of in the BasicQueryHandler. I've tested that, and found that the java fallback code for "offset" works just fine. See BasicQueryHandler.getnodes() and BasicQueryHandler.createSQLString()
Mark
