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