That code doesn't exist yet. I was only using it as an example. I'm
curious to know why you would want to use that syntax for insert and
update statements instead of the normal way of doing things. I agree it
would be a useful feature...I'm just curious what other people would
use it for.
--- Michael Schall <[EMAIL PROTECTED]> wrote:
> This is a beautiful thing! I did not know this was a possibility!
> So
> this will create the command object fill the parameters and leave the
> execution to me? I would only use this for inserts and updates so I
> don't really care about the resultMap portion, but this is the exact
> anser to my post months ago about needing to execute code before and
> after the command is executed. What version of code do I need to use
> this functionality?
>
> > Do you have cases where you just need the underlying statement:
> >
> > IMappedStatement mappedStatement =
> > sqlMapper.GetMappedStatement("Select");
> >
> > Then you can execute that statement on your own?
> >
> > // populate IDbCommand and its parameter collection
> > IDbCommand command = mappedStatement.GenerateCommand();
> >
> > Wouldn't you be missing out on the resultMap engine if you do
> things
> > that way?
>
