I've discovered incremental reading in DbInput, it's a good thing
But i need something more.
stage 1 To read data from incremental file "read-only", i.e. not setting further values back to file.
stage 2 If stage 1 ends succuessfully, calculate new values for posting them into incremental file
reasons to do this are:
1. readers are mulptiple but basic values are the same - there's no need to set update rules for each one, it's boring
2. readers use transformed values and some of them simply do not contain data to put back into incremental file
and one more question: is it possible to do such thing not with files but with DB. I mean pass parameters to query which are taken from another query.
But i need something more.
stage 1 To read data from incremental file "read-only", i.e. not setting further values back to file.
stage 2 If stage 1 ends succuessfully, calculate new values for posting them into incremental file
reasons to do this are:
1. readers are mulptiple but basic values are the same - there's no need to set update rules for each one, it's boring
2. readers use transformed values and some of them simply do not contain data to put back into incremental file
and one more question: is it possible to do such thing not with files but with DB. I mean pass parameters to query which are taken from another query.
-
working method is some kind of hack
i use incremental file as a parameter file (and it's lazy because primary graph was based on params) then at the end i update file with query in incremental way
is it legal and will it (i.e. same incremental and parameter format) work on future releases? -
Hello,
this is good way and will work with future 3.X releases.
Something similar can be done with parameter stored in database: read parameter with DBInputTable and pass it to DBJoin, that reads the data itself and stores a new incremental value in dictionary; then read the value from dictionary and update parameter table (see attached graph).
Please sign in to leave a comment.
Comments 2