I just wasted hours scratching my head about an sqlite excpetion raised
during initialization of the androrm database. I only write this here because
I cannot find another way of contacting anyone involved (feel free to mark this
as solved immediately...).
The trouble stemmed from the fact that I foolishly named a class Transaction
and then tried to manage it via androrm... Maybe you could escape the class
names in the sql statements? Or just put up a big red warning to not used sql
reserved keywords as class names.
Haha. Thanks for pointing that out. I'll add some test case for that and try to somehow escape table names in queries, so that these kinds of errors won't occur :)
I just wasted hours scratching my head about an sqlite excpetion raised during initialization of the androrm database. I only write this here because I cannot find another way of contacting anyone involved (feel free to mark this as solved immediately...).
The trouble stemmed from the fact that I foolishly named a class Transaction and then tried to manage it via androrm... Maybe you could escape the class names in the sql statements? Or just put up a big red warning to not used sql reserved keywords as class names.