-
Notifications
You must be signed in to change notification settings - Fork 16
Support for immutable POJO
xcesco edited this page May 23, 2019
·
1 revision
Sometimes you need to work with an immutable object. Kripton manages this kind of POJO. To be considered immutable a POJO must have a constructor with all fields and all properties only with getter. This works with Kotlin too.
@BindType
public class Person {
@BindSqlColumn("birth")
@BindAdapter(adapter = DateAdapter.class)
private Date birthDate;
private long id;
private String name;
private String surname;
/**
* Constructor
*/
public Person(long id, String name, String surname, Date birthDate) {
super();
this.id = id;
this.name = name;
this.surname = surname;
this.birthDate = birthDate;
}
public Date getBirthDate() {
return birthDate;
}
public long getId() {
return id;
}
public String getName() {
return name;
}
public String getSurname() {
return surname;
}
}
- Introduction
- Goals & Features
- Kotlin
- Immutable or Mutable Pojo
- Annotation Processor Args
- Credits
- Articles
- Benchmarks
- Setup
- Tutorial
- Usage
- Dependencies and inspirations
- Stackoverflow
- Documentation
- SQL logging
- Data source options
- Indices
- SQL Type adapter
- Global SQL Type adapter
- Constraints
- Live data: welcome Architectural components!!
- Paged Live data
- Dynamic parts
- Transactional and batch operations
- Async Transactional and batch operations
- Global transaction
- Support for immutable POJO
- Generate Content provider
- Generate Database schema generation
- Database migration
- BindSqlColumn
- BindContentProvider
- BindContentProviderEntry
- BindContentProviderPath
- BindDao
- BindDaoMany2Many
- BindDataSource
- BindDataSourceOptions
- BindDataSourceUpdateTask
- BindIndex
- BindSqlRelation
- BindSqlAdapter
- BindSqlChildSelect
- BindSqlDelete
- BindSqlDynamicOrderBy
- BindSqlDynamicWhere
- BindSqlDynamicWhereParams
- BindSqlInsert
- BindSqlPageSize
- BindSqlParam
- BindSqlSelect
- BindSqlUpdate
- BindSqlType
- BindSqlTransaction