Torch ORM Alpha 3

The Alpha 3 release brings some important features. There are also changes in the API which might render your code invalid if you already used Alpha 1.

Torch is not just Android anymore

The biggest change is that Torch no longer depends on Android. We decided to remove the dependency by introducing DatabaseEngine interface. By implementing it, you can add support for other databases. For example you might want to implement MySQLDatabaseEngine to let Torch work with MySQL database. Right now there is just one engine in Torch and that is AndroidSQLiteEngine and you can find it in torch-android module.

torch-android module

As was already said, there is only one implementation of the DatabaseEngine and that is for Android's SQLite database. In the torch-android module there is the new convenience class for Torch initialization. Instead TorchService.with(Context) you should be using TorchAndroid.with(Context), which will create a new instance of AndroidSQLiteEngine for you from the provided Context.

Better test coverage

We have put even more effort into testing and added some tests for torch-compiler. In case you would be interested in writing your own implementation of DatabaseEngine, then look up two abstract tests AbstractFilterTest and AbstractMigrationTest which provides consistent set of tests for each engine implementation.

More to come

Even though we did many changes in the past months, there is still a lot more to come and to be added into upcoming versions of the Torch. And remember, pull requests, issue reports and feature requests are always welcome.

(Skipped) Torch ORM Alpha 2

Due to a wrong maven configuration, the release to Maven Central failed. For that we are skipping this release and please see the information about the Alpha 3 release to see what's new.

Torch ORM Alpha 1

1.0-alpha-01

[maven-release-plugin]  copy for tag 1.0-alpha-01