Creating foreign key constraints in ORMLite under SQLite

To elaborate on Gray's awesome answer (for anyone else who stumbles upon this question), you can use the columnDefinition annotation to define a foreign key constraint and cascading delete.

First, foreign key constraints were added to SQLite in 3.6.19, which means you can use them in Android 2.2 or higher (since 2.2 ships with SQLite 3.6.22). However, foreign key constraints are not enabled by default. To enable them, use the technique from this answer.

Here's an example using the columnDefinition annotation. This assumes your table/object you are referencing is called parent which has a primary key of id.

@DatabaseField(foreign = true,      columnDefinition = "integer references parent(id) on delete cascade")private Parent parent;

Note that the format for the String value does not include the column name (that's what the columnName annotation is for).

how to configure my database to enforce valid foreign keys, or perform cascaded deletes without explicit code overhead.

ORMLite supports a columnDefinition="..." field in the @DatabaseFiled annotation @Timo. I'm not sure if it provides you the power you need but it does allow you to have custom column definitions.

http://ormlite.com/javadoc/ormlite-core/com/j256/ormlite/field/DatabaseField.html#columnDefinition()

If it doesn't then I'm afraid that you may have to create your database outside of ORMLite in this case. You can use TableUtils.getCreateTableStatements() to get the statements necessary to create the table and add the enforcement and cascade statements that you need. Here are the javadocs for that method.

I think the next link can be helpful:

http://mueller.panopticdev.com/2011/03/ormlite-and-android.html

in short, you can set it as :

public class Person {...@DatabaseField(columnName = "organization_id", canBeNull = false)private Organization m_organization;

This way, Person has a foreign key to Organization, and the key it uses on Organization is "organization_id" .

Hope this helps.