You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Dan Turkenkopf (JIRA)" <ib...@incubator.apache.org> on 2008/05/03 01:04:55 UTC
[jira] Created: (IBATIS-505) Add runtimeSchemaName property to
Ibator to allow for overriding default schema name
Add runtimeSchemaName property to Ibator to allow for overriding default schema name
------------------------------------------------------------------------------------
Key: IBATIS-505
URL: https://issues.apache.org/jira/browse/IBATIS-505
Project: iBatis for Java
Issue Type: New Feature
Components: Tools
Reporter: Dan Turkenkopf
The customer I'm working with uses multiple schema for each application - one for the application owner where the tables are created, and one for use by the application that uses aliases and restricted permissions to access the tables (for example APPLICATION_OWNER and APPLICATION)
They'd like to use the application level schema as the reference schema for the SQL maps.
Abator (and I'm assuming Ibator) needs to run against the owner schema, but should create the SQL maps and objects referring to the application schema.
To accomplish this, I created a new property "runtimeSchemaName" that behaves in the same manner as "runtimeTableName".
The example usage would be <property name="runtimeSchemaName" value="APPLICATION">
I'll attach a patch that includes the changes. I'm fairly new to Subversion and patching, so I apologize if things didn't come out completely correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (IBATIS-505) Add runtimeSchemaName property to
Ibator to allow for overriding default schema name
Posted by "Jeff Butler (JIRA)" <ib...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/IBATIS-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Butler closed IBATIS-505.
------------------------------
Resolution: Fixed
Fixed in SVN - thanks for the patch!
BTW - I changed the property name to "runtimeSchema" versus "runtimeSchemaName" to keep consistency. I also added support for "runtimeCatalog" just in case anyone might need that.
> Add runtimeSchemaName property to Ibator to allow for overriding default schema name
> ------------------------------------------------------------------------------------
>
> Key: IBATIS-505
> URL: https://issues.apache.org/jira/browse/IBATIS-505
> Project: iBatis for Java
> Issue Type: New Feature
> Components: Tools
> Reporter: Dan Turkenkopf
> Assignee: Jeff Butler
> Attachments: ibator_runtimeschemaname.patch
>
>
> The customer I'm working with uses multiple schema for each application - one for the application owner where the tables are created, and one for use by the application that uses aliases and restricted permissions to access the tables (for example APPLICATION_OWNER and APPLICATION)
> They'd like to use the application level schema as the reference schema for the SQL maps.
> Abator (and I'm assuming Ibator) needs to run against the owner schema, but should create the SQL maps and objects referring to the application schema.
> To accomplish this, I created a new property "runtimeSchemaName" that behaves in the same manner as "runtimeTableName".
> The example usage would be <property name="runtimeSchemaName" value="APPLICATION">
> I'll attach a patch that includes the changes. I'm fairly new to Subversion and patching, so I apologize if things didn't come out completely correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.