0004397: django bank should load initial data in the initial migration

ID	Project	Category	View Status	Date Submitted	Last Update
0004397	Taler	obsolete component	public	2016-04-11 15:30	2016-04-13 14:20

Reporter	Florian Dold	Assigned To	Marcello Stanisci	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	won't fix
Product Version	0.0
Target Version	0.0	Fixed in Version	0.0

Summary	0004397: django bank should load initial data in the initial migration
Description	It should not be a separate management command. Especially not one that is run in every view.
Tags	No tags attached.

Date Modified	Username	Field	Change
2016-04-11 15:30	Florian Dold	New Issue
2016-04-11 15:30	Florian Dold	Status	new => assigned
2016-04-11 15:30	Florian Dold	Assigned To	=> Marcello Stanisci
2016-04-13 09:26	Marcello Stanisci	Note Added: 0010462
2016-04-13 09:26	Marcello Stanisci	Status	assigned => informing
2016-04-13 09:26	Marcello Stanisci	Resolution	open => won't fix
2016-04-13 14:20	Christian Grothoff	Status	informing => closed
2016-04-13 14:20	Christian Grothoff	Product Version	=> 0.0
2016-04-13 14:20	Christian Grothoff	Fixed in Version	=> 0.0
2016-04-13 14:20	Christian Grothoff	Target Version	=> 0.0
2022-08-23 18:26	Christian Grothoff	Category	bank (demonstrator) => py bank (demonstrator, obsolete)
2023-12-03 00:23	Christian Grothoff	Category	py bank (demonstrator, obsolete) => obsolete componet
2023-12-11 19:08	Florian Dold	Category	obsolete componet => obsolete component

Marcello Stanisci 2016-04-13 09:26 reporter ~0010462	not a bug since 'flush' cannot delete data inserted along initial migrations