Releases: javrasya/django-river
Releases · javrasya/django-river
0.6.2
- Bug - Migration
0002
and0003
were not working properly for postgresql (maybe oracle). For these databases, data can not be fixed. Because, django migrates each in a transactional block and schema migration and data migration can not be done in a transactional block. To fix this, data fixing and schema fixing are separated. - Improvement - Timeline section is added into documentation.
- Improvement - State slug field is set as slug version of its label if it is not given on saving.
0.6.1
- Bug - After
content_type
andfield
are moved intoProceedingMeta
model fromTransition
model in version0.6.0
, finding initial and final states was failing. This is fixed. - Bug -
0002
migrations was trying to set default slug field of State model. There was a unique problem. It is fixed.0002
can be migrated now. - Improvement - The way of finding initial and final states is changed. ProceedingMeta now has parent-child tree structure to present state machine. This tree structure is used to define the way. This requires to migrate
0003
. This migration will build the tree of your existed ProceedingMeta data.
0.6.0
- Improvement -
content_type
andfield
are moved intoProceedingMeta
model fromTransition
model. This requires to migrate0002
. This migrations will move value of the fields fromTransition
toProceedingMeta
. - Improvement - Slug field is added in
State
. It is unique field to describe state. This requires to migrate0002
. This migration will set the field as slug version oflabel
field value. (Re Opened -> re-opened) - Improvement -
State
model now hasnatural_key
asslug
field. - Improvement -
Transition
model now hasnatural_key
as (source_state_slug
,destination_state_slug
) fields - Improvement -
ProceedingMeta
model now hasnatural_key
as (content_type
,field
,transition
,order
) fields - Improvement - Changelog is added into documentation.
0.5.3
0.5.2
- Improvement - Removed unnecessary models.
- Improvement - Migrations are added
- Bug -
content_type__0002
migrations cause failing fordjango1.7
. Dependency is removed - Bug -
DatabaseHandlerBacked
was trying to access database on django setup. This causeno table in db
error for some django commands. This was happening; because there is no db created before some commands are executed; likemakemigrations
,migrate
.