[
https://issues.apache.org/jira/browse/IBATIS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680359#action_12680359
]
Jeff Butler commented on IBATIS-586:
------------------------------------
Couple of questions....
1. For the use case you describe, why can't you just use a column override and
rename the property whatever you want?
2. I understand that there could be times when you might want to send a column
based property to a plugin. I've got a simpler suggestion....how about adding
something like a userProperty or userString attribute to column override. You
could attach whatever String you wanted to a column and a plugin could retrieve
it.
> 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.
