ibatis-dev mailing list archives

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

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

Dan Turkenkopf commented on IBATIS-586:

How about a compromise to your compromise?  

A single string underneath the columnOverride but it's parsed by Ibator and stored as actual

If we make ColumnOverride extend PropertyHolder, then all that's needed is to write the parsing
logic.  I'd prefer something where the framework handles the parsing because it would make
it a lot easier to use third-party plugins without worrying (as much) if they conflicted with
other plugins.

If you're okay with that approach I can make the changes tonight.

> 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