Transitive closure table not maintained when new data generated

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Generate 100 patients with MI (add new always)
2. Generate 100 patients with Injury anatomical structure (add new always)
3. Query for pts with MI
4. Query for pts with Injury anatomical structure
5. Query for Injury anatomical structure, with morphology of necrosis

What is the expected output? 

Response to (5) should be less than response to (4)

What do you see instead?

Response to (5) is more than response to (4) 

Patients with MI are not being retrieved by (4), but are by (5)

Original issue reported on code.google.com by jeremy.r...@googlemail.com on 24 Jan 2011 at 4:52

[GoogleCodeExporter]

Presumably, this mis-reporting can be fixed by running the menu option to 
generate a comprehensive transitive closure table for the current enumerated 
library of unique expressions.

Original comment by jeremy.r...@googlemail.com on 24 Jan 2011 at 4:55

[GoogleCodeExporter]

...but algorithm to generate TC table runs out of java heap (where maxheap is 
whatever the exe sets it to) with 200 pts generated as above.

Original comment by jeremy.r...@googlemail.com on 24 Jan 2011 at 5:15

[GoogleCodeExporter]

The way to fix this issue to force TC generation for the query, by asking 
Snofyre to ignore 'TC table'. You can set this in the Query Execution 
Optimisations Panel in the left side bar....

Comprehensive TC generation will definitely exceed Snofyre's current -Xmx 
limit! So this is a no go for the moment... Needs more investigation (SNOMED CT 
Reporting Project T3 volumetric + performance testing)

Original comment by jay.kola on 25 Jan 2011 at 12:08