Mark Lewis <mark.lewis@mir3.com> writes:
> JDBC is a little too low-level to give true database independence; you
> can write portable queries, but you're severely restricted when it comes
> to functionality supported by most databases but not in a standardized
> way, such as limits, locking, performance hinting, sequences/serials,
> etc.
>
> For simple, non-performance critical apps you can mostly get away with
> it (as we did for a while with some of our products). But for anything
> more sophisticated, your application really needs a way to deal with
> database-specific SQL.
Thanks a lot for sharing this very valuable experience from the
field. However .setMaxRows() IS currently part of this portable and
severely restricted JDBC performance feature set, so I see no reason
for not trying to implement it as best as possible.
The more performance you can get from JDBC, the less not portable code
people will write.
And JDBC is evolving too.