Jooq is actually excellent as SQLite query builder. You can also take a look at the Android JDBC driver SQLDroid <https://github.com/SQLDroid/SQLDroid> though honestly, I would stay away from using JDBC driver (check out the open issues if it'll affect your usage) and opt for the provided platform API instead.
Also, it's easier to have a running local SQLite database on your computer and generate the needed code (mostly POJOs + global Tables and Column) to be used on Android. Pair it with Flyway for easier migration (linky <http://flywaydb.org/documentation/database/sqlite.html>) or just utilize SQLiteOpenHelper. You might also need to check out which SQLite version though I expect the DSL doesn't change that much between Android versions. Here's an SO post for Android specific SQLite versions. <http://stackoverflow.com/questions/2421189/version-of-sqlite-used-in-android> As for my personal experience, I find that using ORMs (or simply just Cupboard <https://bitbucket.org/littlerobots/cupboard>) are much easier to manage (and far less headache) than utilizing SQLite directly due to the increasingly flexible nature of data models on mobile. Couple that with the highly impermanent data retention plus the common suggestion to simply drop the whole table instead of upgrading manually each time on Android. (Of course, you can always go nuts with the Android SharedPreferences... if you have even lesser requirements ;-) ) It really depends on your project requirement in the end. On Wednesday, January 6, 2016 at 7:21:58 PM UTC+8, [email protected] wrote: > > Hi, > > I was wondering if JOOQ can be used in Android project without any > problems. Do you have support for Android or anybody using it on his > project, that can share experiences? > > Tomas. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
