I think they do encourage personally contributions, I'm little
surprised that they haven't asked you to do so.

The way we did it was kind of "backdoor", depend on the detail sqlmap
implementation:
SqlMapExecutorDelegate delegate = ((ExtendedSqlMapClient)sqlMap).getDelegate();
then delegate.getMappedStatementNames() will return an iteration of
all the available statements. So we put these into a map and does the
lookup by ourselves. This is definitely not the way we should use the
sqlMapClient, but it's important for us to have this ability now.

-Scott


On Mon, 28 Mar 2005 22:00:19 +0200 (CEST), Vadim Pesochinskiy (JIRA)
<[email protected]> wrote:
>     [ 
> http://issues.apache.org/jira/browse/IBATIS-87?page=comments#action_61668 ]
> 
> Vadim Pesochinskiy commented on IBATIS-87:
> ------------------------------------------
> 
> How did you implement this? Do you parse the SqlMap config in your code? I am 
> hesitating doing that, because changes in config will make your code not 
> usable. I would not mind doing this, if it was available in the next release 
> instead of being my "proprietary" extension.
> 
> Current solution, which Clinton described above, is acceptable, but I would 
> prefer to keep all SQLs in one place.
> 
> This is very unfortunate that one cannot easily add contributions to the 
> project, because it kind of undermines the value of open source... On the 
> other hand, managing the scope is more important than ability for everyone to 
> add code.
> 
> > Add notion of DB specific SQL statements
> > ----------------------------------------
> >
> >          Key: IBATIS-87
> >          URL: http://issues.apache.org/jira/browse/IBATIS-87
> >      Project: iBatis for Java
> >         Type: New Feature
> >   Components: SQL Maps
> >  Environment: Any
> >     Reporter: Vadim Pesochinskiy
> >     Priority: Minor
> 
> >
> > This is probably not very impressive idea, but I will throw it in anyway.
> > What if we add a DatabaseType property and have SqlMap lookup proper query 
> > for it in the same manner as Java internationalization works. DB type 
> > attribute can have an arbitrary value, which is only used get proper query.
> > E.g.
> > Queries:
> >   getOrder.sqlserver
> >   getOrder
> > If DataBaseType is 'sqlserver' - 'getOrder.sqlserver' query is picked, if 
> > DataBaseType=oracle or DataBaseType=postgres 'getOrder' sql will be 
> > executed.
> > I can implement it, if you don't mind :). Thanks.
> 
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>   http://issues.apache.org/jira/secure/Administrators.jspa
> -
> If you want more information on JIRA, or have a bug to report see:
>   http://www.atlassian.com/software/jira
> 
>

Reply via email to