ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "alan do (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Created: (IBATIS-187) Sql Mapper constraint under dynamic schema name as stored procedure prefix change on various deployment environments
Date Thu, 25 Aug 2005 16:04:08 GMT
Sql Mapper constraint under dynamic schema name as stored procedure prefix change on various
deployment environments
--------------------------------------------------------------------------------------------------------------------

         Key: IBATIS-187
         URL: http://issues.apache.org/jira/browse/IBATIS-187
     Project: iBatis for Java
        Type: Improvement
  Components: SQL Maps  
    Versions: 2.1.0    
 Environment: all
    Reporter: alan do
    Priority: Minor


The stored procedure names are hard-coded inside individual SQL Mapper XML. This causes problems
when deploying the same build from development to QA then to Production when the stored procedure
names change. In the majority of the cases, the name change is in the schema. For example,
'call DBSCMDEV.SP001 (?,?)' must be changed to 'call DBSCMPROD.SP001 (?,?)'  in production.
This is common when DB instances are installed on the same (mainframe) to serve 3 environments
(dev, qa, production). There are work-arounds, but all require duplication of the XMLs (sometimes
up to 100 SqlMaps.xml for each app).

It would be nice if there is a way to dynamically pass in SP prefixes, and possibly other
parameters, from an external properties file when the SqlMapDao's are initialized...or make
the <procedure> config more configurable.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message