Thanks for the tip. its really good news to me.

As for running into Database locks, i find that strange … AFAIK, sqlite supports concurrent access from within the same process. i.e. its thread-safe. Its not multi-process-save, but it is multi-thread-safe. further investigation is needed to validate my argument of course.

- Drop the JDBC Driver in your libs/ directoy
- Write a Hibernate SQLite Dialect (I found on on the web: http://elbart0.free.fr/SQLiteDialect.java.txt)
- Adjust the DataSource settings with the SQLite-specific settings. Especially, you need to indicate your SQLite Dialect since Grails won’t detect it by itself.

That should work. However, keep in mind that SQLite is not a multi-user database engine. I ran into the “Database Locked” problem (just search the web for this issue and you know what I mean), which I suspect, has to do with concurrent users. Therefore I would not recommend using SQLite in a web application.

Thanks for the tip.

I’ve done some research and found that SQLite is not Hibernate friendly (at least not yet). Which is really sad for such a great engine.

I wonder if there is any initiative on this matter, as this would be a great boon for grails.
- Kefah.

The universal library will by default use a native library, but revert back to the pure Java version if a suitable lib cannot be found, conn.getDriverVersion() will return “native” if a native lib is being used.

The old format of separate jars is still provided, so to chose one or the other use the appropriate jar.

Tom

Thanks for the tip Tom.

So, does that obsolete xerial library and how can we choose between native and pure java?

- Kefah.

Tom