This has been long on my wishlist. It would be really nice to have a "pass through" derivation that does not attempt to be compiled but simply passed through to the Output link. This will allow the developer to not have to use as many Hash lookups or user-defined SQL.
I want to be able in the Transformer to specify in a column derivation:
Derivation Column Name
VERSION+1 VERSION
FKEYSEQUENCE.NextVal Fkey_Sequence
VERSION will have an SQL type of (SQL).
UPDATE <<table>>
Set VERSION = VERSION+1,
Fkey_Sequence=FKEYSEQUENCE.NextVal
SQL (pass through) datatype
Re: SQL (pass through) datatype
This is a response based on 6.x:1stpoint wrote:This has been long on my wishlist. It would be really nice to have a "pass through" derivation that does not attempt to be compiled but simply passed through to the Output link. This will allow the developer to not have to use as many Hash lookups or user-defined SQL.
I want to be able in the Transformer to specify in a column derivation:
Derivation Column Name
VERSION+1 VERSION
FKEYSEQUENCE.NextVal Fkey_Sequence
VERSION will have an SQL type of (SQL).
UPDATE <<table>>
Set VERSION = VERSION+1,
Fkey_Sequence=FKEYSEQUENCE.NextVal
With Server (at least with Oracle), you can create an user-defined SQL that contains that very same thing. However, this would be an excellent feature to add for PX. Right now, we use a custom stage to handle the .NextVal concept.
-T.J.
Developer of DataStage Parallel Engine (Orchestrate).
user-defined SQL, just say no.
This is exactly the scenario I am trying to avoid. If we have to resort to user-defined SQL we then need an added level of maintenance to something that could be automated via a SQL/passthrough.With Server (at least with Oracle), you can create an user-defined SQL that contains that very same thing.