You know I'm looking for a more generic way to model my application.
So first I tried it with a <Results> exit of type "Anything". The retrieved records should be packaged in a "Data Structure" with the record id an table name explicitly noted. This generic data structure could now be passed through the application.
The problem is, that this leads to the error, that Tersus can't build an instance of "Anything".
Therefore - remembering what I have seen in the "Database Viewer" - I thought over a solution with the "Map" element.
To get a result from "Database Query" as "Map" is no problem.
But how to pass a "Map" (key=columnname; value=value) to a "Database Update" (DU) element without explicitly naming the DU-triggers with the concrete keys of the "Map"?
The <SQL Statement> string should be composed before. But to go through all elements of a map (and not knowing the keys) an iterator ("Get next Map Entry" or sth. like that) is needed.
ciao, kkg
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
