| 1 |
|
2010-10-04 Torsten Irländer <[email protected]> |
| 2 |
|
|
| 3 |
|
* formed/formed/model/data.py (RuleLeaf.__init__): Added new attribute |
| 4 |
|
"tag" for rule-leafs |
| 5 |
|
* formed/formed/config.py: Added export rules as XML to Menu |
| 6 |
|
* formed/formed/plugins/modify/rules.py |
| 7 |
|
(GenerateRequiredRules.generateDateSequenceRules): Generate automatic |
| 8 |
|
tag ids for date-sequence rules |
| 9 |
|
|
| 10 |
|
2010-09-30 Torsten Irländer <[email protected]> |
| 11 |
|
|
| 12 |
|
* formed/formed/plugins/export/rules_sh.py |
| 13 |
|
(ExportRulesAsSH.doExport): Filter out duplicted rules. |
| 14 |
|
|
| 15 |
|
2010-09-20 Frank Koormann <[email protected]> |
| 16 |
|
|
| 17 |
|
* formed/formed/plugins/export/latex.py (RecursiveExporter): |
| 18 |
|
Add "required"-field information to output and include |
| 19 |
|
choice list contents. |
| 20 |
|
|
| 21 |
|
2010-09-16 Bernhard Herzog <[email protected]> |
| 22 |
|
|
| 23 |
|
Avoid database deadlocks that can happen when database clients try |
| 24 |
|
to work with the same case using two separate database |
| 25 |
|
connections. See mpuls/issue1145 for details. |
| 26 |
|
|
| 27 |
|
* formed/formed/plugins/export/rg_sql.py (SQL_TEMPLATE): Split the |
| 28 |
|
computation of the new json structure description into the new |
| 29 |
|
database function compute_case_structure |
| 30 |
|
(TRIGGER_TMPL): Change the trigger functions to immediately update |
| 31 |
|
the cached json structure description instead of just setting the |
| 32 |
|
modified flag. This avoids the lazy recomputation that makes what |
| 33 |
|
seems like a read-only access (calling get_case_structure) into a |
| 34 |
|
writing access (updates of the cache). The writes lock the row in |
| 35 |
|
the case_structure table which prevent other connections from |
| 36 |
|
accessing the same case. As part of this, the delete triggers are |
| 37 |
|
now AFTER triggers because the repeat groups instance must have |
| 38 |
|
been removed when the structure is recomputed. |
| 39 |
|
(SUBSELECT_TMPL): Since the delete trigger is now an after |
| 40 |
|
trigger, we need to change the way the master id is computed. We |
| 41 |
|
cannot join with the repeatgroup table in question because the row |
| 42 |
|
has already been deleted. However, we can use the master_id |
| 43 |
|
column of the OLD row to select the row of the parent table. |
| 44 |
|
(create_triggers): Avoid the inner joins with the current repeat |
| 45 |
|
group for the above mentioned reasons. In the very common case of |
| 46 |
|
repeat groups which are direct children of the master_tbl, we can |
| 47 |
|
compare the master_tbl.id directly with the row's master_id. |
| 48 |
|
|
| 49 |
2010-09-14 Roland Geider <[email protected]> |
2010-09-14 Roland Geider <[email protected]> |
| 50 |
|
|
| 51 |
* formed/formed/plugins/export/xsd.py: issue1131: update XSD for new |
* formed/formed/plugins/export/xsd.py: issue1131: update XSD for new |
Parent Directory
| 
Revision Log
| 
Patch