DBeaver Forum

Hello,

Generally ODBC error "Option value changed" means that some feature isn't supported but it should be a warning, not an error. Probably DBeaver fails on some not-necessary operation over resultset and we can handle it more correctly.
Could you attach/paste full error description? It is available in error log view (main menu -> Windows). Just copy esxception stacktrace.

Thanks!

Hi,

Yes, setMaxRows throws an exception. Generally JDBC drivers sinlently ignore this parameter if they do not support it.
Anyway, fix of this problem will be included in the 2.0 final release version (on the next week).

Thanks for report!