When does Mercator commit database transactions 6.7

[Skiergirl]

Hi,

I have a runmap that commits one row to a table each time the map is called. The runmap is being called multiple times by a control map. The commit scope for the table output card is set to "map".

The question is, with these settings, shouldn't the runmap commit the transaction each time it is called or does the control map override that setting?

Andrea

 

[eyetry]

From my experience, depending on your map design, the control map has overridden the map settings.

I did have one set of maps that had an issue similar to what you described. The cntl map would execute a runmap that tested the status of data in some temp tables. If the condition was right it would truncate the table(s). There were also some inserts going on in other related maps. Anyway, I ended up using functional maps. I had an extra element in each group handled by the funtional map. that element had a commit stmnt in it.

The solution was less than ideal but it worked and had slew of critical things on the plate at the time. Just tried to knock them down.