Skip to content

SQLite ORM Constraints

xcesco edited this page Mar 7, 2018 · 2 revisions

There are some constraint to respect to get Kripton working well as light ORM:

  • Every table must have a long primary key. Said in other words, every model object have to contain a field long used as primary key.
  • Every DAO can produce/insert/update only model object of its declared bean type. This means that you can also use inner join or whatever, but when you use a select you can extract only columns of model associated to the DAO interface.

Table of Contents

Query definition

Features

Relations

Multithread supports

Modularization

Annotations for data convertion

Annotations for SQLite ORM

Annotations for shared preferences

Clone this wiki locally