QueryBuilder limit has problem in jdbc with Oracle about ormlite-jdbc HOT 8 CLOSED

This is for oracle? Can you try overriding the default OracleDatabaseType and the following method. You can then pass the custom database type to the JdbcConnectionSource constructor. Does that work? If it does I will make the change in trunk and it will be in the next release. Unfortunately I don't have access to an Oracle database to test ORMLite. :-(

public boolean isLimitAfterSelect() {
    return true;
}

from ormlite-jdbc.

Use H2 now, can not make a test, sorry.Love OrmLite, simple and easy. :)

from ormlite-jdbc.

H2 doesn't work with limit? I'm very surprised since it is my test DB and I have a ton of test coverage around limit. Can you write a small unit test that fails for you?

from ormlite-jdbc.

No, I mean H2 is ok . everything is fine when I switch to H2.

from ormlite-jdbc.

This still an Issue under odbc, should keep open ?

from ormlite-jdbc.

Oh, ok. Yeah, let's leave it open.

from ormlite-jdbc.

I'm going to close this because I can't figure out what the appropriate Oracle fu is. Someone is free to reopen if they have more information.

from ormlite-jdbc.

Hi! I'm having this exact same problem. The exception after the change is the following:
java.sql.SQLSyntaxErrorException: ORA-00923: FROM keyword not found where expected
before the change it was:
java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended

Any other suggestions?

Thanks!

from ormlite-jdbc.