ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Butler (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Commented: (IBATIS-586) Allow custom properties for columns
Date Tue, 10 Mar 2009 14:52:52 GMT

    [ https://issues.apache.org/jira/browse/IBATIS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680494#action_12680494

Jeff Butler commented on IBATIS-586:

I don't care for that approach.  If we really need to support multiple properties then we
should make it consistent with the rest of Ibator and do it with nested property elements.
 Consistent XML, consistent documentation, code reuse.

I think that's the way to go.  I can probably get to it sometime today - it won't take long.

> Allow custom properties for columns
> -----------------------------------
>                 Key: IBATIS-586
>                 URL: https://issues.apache.org/jira/browse/IBATIS-586
>             Project: iBatis for Java
>          Issue Type: New Feature
>          Components: Tools
>    Affects Versions: 2.3.3
>            Reporter: Dan Turkenkopf
>         Attachments: ibator-column-configuration.txt
> Ibator allows you to create nest custom property tags at the table level which are quite
useful in configuring plugins.
> However there's no way to provide the same capabilities on a column by column basis.
> The use case that drove me to add this feature is the need to capitalize certain columns
(first name and last name, etc) but not all the columns in the table.
> The attached patch adds an optional <column> tag underneath each <table>.
 The column tag supports the nesting of property tags underneath it for custom properties.
 It's possible that the ignoreColumn and columnOverride tags could be subsumed by the column
tag but it's not necessary.
> An alternate approach would be to create <columnProperty> tags that have the column
and the property name and value defined as a single tag. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message