Thanks again Jason.

On Apr 6, 1:04 pm, Jason Meckley <[email protected]> wrote:
> you mean the parameter of the command is an output parameter? for that
> you could build you own operation. ConventionInputCommandOperation is
> designed to return rows from a query. ConventionOutputCommandOperation
> is meant to execute non-query operations like insert, delete, update.
> the AddParameter is a convenience method to add input parameters. If
> you want to configure output parameters then I would look at
> subclassing either AbstractOperation or AbstractDatabaseOperation and
> configure the command yourself. the Use utility class can assist with
> managing the database connection/transaction.
>
> branching is used to send 1 input to N outputs. for example: query
> table and send rows to a file and another database.
>
> On Apr 6, 11:50 am, Larry R <[email protected]> wrote:
>
> > I have this wonderful database to deal with. I have to query a "seed"
> > table for a unique Id, then do an insert. Yes, really. No, changing
> > the tables is not an option.
>
> > I am a noob at the Rhino ETL, but I am assuming that I would make this
> > part of a Branched operation and set the row["CustomerId"] to the
> > returned value, but can't seem to find any example where an output
> > parameter is used in an operation.
>
> > AM I going about this correctly? if I used a
> > ConventionInputCommandOperation, how do you get the output parameter
> > value?
> > Larry

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.

Reply via email to