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