--- Christopher Bissell <[EMAIL PROTECTED]> wrote:
> *Syntactically, better support in the mapping files for stored
> procedure
> parameters. We like the inline parameter methods you can use with
> dynamic
> SQL, would be nice to have a way to use that with sprocs too.
You mean instead of being required to use a parameterMap and use
question mark place holders:
?, ?, ?
You'd like to use this:
#FirstName#,
#LastName#,
#Age,type=int,dbType=int,handler=FooHandler#
The Java and Dev list are also good lists to sign up up and discuss
things like this too. They get more traffic than this list. The
IBatisNet developers are signed up to all the lists.
> *Better decoupling of SqlMappers from physical databases / db
> connections.
> Decoupling is implicit in the object model, but it's difficult to use
> the
> SqlMapper as 'just' a repository of maps, rather than as an
> abstraction in
> front of a physical database.
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?
- Ron
