[
https://issues.apache.org/jira/browse/OFBIZ-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446816#comment-13446816
]
Jacques Le Roux commented on OFBIZ-5020:
----------------------------------------
Agreed Adrian, I tested it this afternoon on Postgres 9.1. If in a newly
created DB you rename service_name by SERVICE_NAME then on next start OFBIz
will re-create a service_name. By default Postgres is case sensitive (Google
for "Postgres column case sensitive"). I saw MySql (and MSQL I think) can be
tuned for that, anyway I don't use MySql (nor MSQL)
Note: this upper cased field names technique was used in the pre Apache era.
It's easy to find trace in data model looking for col-name (thanks to Nicolas
who mentionned it), but there are no corresponding commits in the Apache repo
(at least I did not find one)
> change serviceName by customMethod on Content
> ---------------------------------------------
>
> Key: OFBIZ-5020
> URL: https://issues.apache.org/jira/browse/OFBIZ-5020
> Project: OFBiz
> Issue Type: Improvement
> Components: content
> Affects Versions: SVN trunk
> Reporter: Nicolas Malin
> Assignee: Jacques Le Roux
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: OFBiz-5020-migrate.patch, OFBiz-5020.patch,
> OFBIZ-5020.patch, OFBIZ-5020.patch, OFBIZ-5020.patch
>
>
> At this time, when you use a content as template, the content.serviceName
> value use to call the context populate service before rendering.
> I propose to replace serviceName field by customMethodId and use customMethod
> pattern for more flexibility.
> serviceName field will be move to oldServiceName field for backward
> compatibility
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
