[
https://issues.apache.org/jira/browse/IBATIS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680365#action_12680365
]
Jeff Butler commented on IBATIS-586:
------------------------------------
1. Ahhh - I get it.
2. The string could be "prop1=Fred;prop2=Wilma;prop3=Betty;prop4=Barney", or
anything else your plugin wanted.
Another way to do this would be to allow the property element under the
columnOverride element.
My preference is just the single string - it's less XML and less API and would
work in all cases. It does require a plugin to parse the string if there is
more than one property.
Slightly less preferable for me (because of the extra verbocity of the XML)
would be to add property nested under columnOverride. This is more XML but not
much more API. The reason I prefer this instead of an entire new element like
column or columnProperty is just to keep things simple - we already have a tag
that would work, we should use it.
I guess I could go either way.
> 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.
