You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Mike Haller (JIRA)" <ib...@incubator.apache.org> on 2008/12/16 12:36:44 UTC
[jira] Created: (IBATIS-566) Code generation for multiple DB
vendors
Code generation for multiple DB vendors
---------------------------------------
Key: IBATIS-566
URL: https://issues.apache.org/jira/browse/IBATIS-566
Project: iBatis for Java
Issue Type: Improvement
Components: Tools
Environment: ibator 1.2.0.665
Reporter: Mike Haller
Ibator Configuration File (and Templates) should be improved to better support the generation for multiple database vendors:
- Possibility to disable the generation of DTOs: javaModelGenerator should not be required. The DTOs are already generated in one of the previous generations and all following generations should reuse the existing DTOs
- Generator should be able to parse DDLs instead of requiring a live database: when code is generated in the build process, it is desirable to be able to generate code without the need for a live database instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IBATIS-566) Code generation for multiple DB
vendors
Posted by "Jeff Butler (JIRA)" <ib...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/IBATIS-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657055#action_12657055 ]
Jeff Butler commented on IBATIS-566:
------------------------------------
Regarding disabling DTOs - this can be accomplished with a near-trivial plugin. I'm hesitant to make javaModelGenerator optional as the generated SQL is 100% coupled with the generated DTOs. If you are willing to take the risk that the DTOs would mis-match the generated SQL, then I think that implementing a plugin to kill the DTOs is a reasonable amount of effort to ask you to go through.
Regarding parsing of DDL - this is a big job. An SQL parser is non-trivial to implement - I would probably want to use ANTLR to generate a parser and maintain a somewhat standard SQL grammer. This could also be accomplished with a plugin if you (or someone else) is willing to invest the effort to do it.
> Code generation for multiple DB vendors
> ---------------------------------------
>
> Key: IBATIS-566
> URL: https://issues.apache.org/jira/browse/IBATIS-566
> Project: iBatis for Java
> Issue Type: Improvement
> Components: Tools
> Environment: ibator 1.2.0.665
> Reporter: Mike Haller
>
> Ibator Configuration File (and Templates) should be improved to better support the generation for multiple database vendors:
> - Possibility to disable the generation of DTOs: javaModelGenerator should not be required. The DTOs are already generated in one of the previous generations and all following generations should reuse the existing DTOs
> - Generator should be able to parse DDLs instead of requiring a live database: when code is generated in the build process, it is desirable to be able to generate code without the need for a live database instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.