I am not saying that it's not useful or needed. Every case you
describe is dead-on.
What I am saying is that IMO, this is not something that iBATIS should do.
Why?
Because all of the cases you describe happen if I use iBATIS or any
other technology - so why should it be exclusive to iBATIS?
It
On 11/8/06, Larry Meadors <[EMAIL PROTECTED]> wrote:
-1
Even though I haven't used the C# version in months, I agree with Gilles.
This sort of thing is the domain of a separate project, not iBATIS -
it has precious little to do with data mapping.
The use case is being able to switch datasourc
You can place them in the web.config/app.config
and initialize a session variable "ConnectionString" that is init with the choice of the user and used in the per user datasource-- Cheers,Gilles
http://www.amazon.com/gp/registry/6JCP7AORB0LE">Wish List
-1
Even though I haven't used the C# version in months, I agree with Gilles.
This sort of thing is the domain of a separate project, not iBATIS -
it has precious little to do with data mapping.
Larry
On 11/7/06, Gilles Bayon <[EMAIL PROTECTED]> wrote:
-1
I think the configuration file must r
Do you have any suggestions of how we could specify multiple
connection strings in the configuration without creating a second set
of maps?
I like the notion of being able to have per-user connection strings,
but "Separation of Concerns" tells us that's its wrong to specify the
connection strings
-1
I think the configuration file must remain simple as possible.
iBATIS main core is not here to fill 100% of your need but must be extensible to allow you deal with your custom requirement.
I have try to design things so that you can extends it, indeed I hope :-)-- Cheers,Gilleshttp://www.amazon.
As to
* http://opensource.atlassian.com/confluence/oss/x/uhc
In a future release, what if we allow multiple databases to be set in
the configuration, and then retrieved via a helper class? Maybe
something like
public class PerUserDataSource : DataSource
{
ISqlMapper _ISqlMapper = null
