bugfix: an asset associated to default successor didn't appear in the printout.

cause: the default successor (id=0) is loaded on startup (kind of a fixture)
but it wasn't comitted and therefore the hasMany property wasn't updated when
the asset were saved.
This commit is contained in:
git@daemon.de
2013-09-13 08:09:19 +02:00
parent b8df33061b
commit 81aa7e83e4
4 changed files with 5 additions and 11 deletions

8
TODO
View File

@@ -1,8 +0,0 @@
- wenn man beim Neuanlegen eines Assets die beiden
Selects (Successor und Order) so lässt wie sie sind,
wird null eingetragen, das Asset taucht nicht im
Testament auf, successor.has_assets returned 0
und das bleibt auch so, wenn man das Asset nach-
träglich ändert.
Supposed Fix: Validate New Asset order+successor.