[
https://issues.apache.org/jira/browse/OFBIZ-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533579
]
Adam Heath commented on OFBIZ-1321:
-----------------------------------
==
alias-view-columns="flase"
==
framework/entity/src/org/ofbiz/entity/config/DatasourceInfo.java:
this.aliasViews =
"true".equals(datasourceElement.getAttribute("alias-view-columns"));
==
So, that setting is false, so the columns are *not* aliased. Your config needs
to be changed.
The default config shipped by ofbiz also needs to be changed.
> SQL creation has changed format in ver 4.0
> ------------------------------------------
>
> Key: OFBIZ-1321
> URL: https://issues.apache.org/jira/browse/OFBIZ-1321
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release Branch 4.0
> Reporter: BJ Freeman
> Assignee: David E. Jones
> Fix For: Release Branch 4.0
>
>
> I update from the latest 4.0 release
> all of a suddent the SQL has under scores where it did not before.
> example
> viewprofile.bsh
> Method Invocation delegator.findByAnd : at Line: 86 : in file:
> component://party/webapp/partymgr/WEB-INF/actions/party/viewprofile.bsh :
> delegator .findByAnd ( "PartyNoteView" , UtilMisc .toMap ( "targetPartyId" ,
> partyId ) , UtilMisc .toList ( "-noteDateTime" ) )
> now produces
> Target exception: org.ofbiz.entity.GenericDataSourceException: SQL Exception
> while executing the following:SELECT PN.PARTY_ID AS TARGET_PARTY_ID,
> ND.NOTE_ID AS NOTE_ID, ND.NOTE_NAME AS NOTE_NAME, ND.NOTE_INFO AS NOTE_INFO,
> ND.NOTE_DATE_TIME AS NOTE_DATE_TIME, ND.NOTE_PARTY AS NOTE_PARTY FROM
> public.PARTY_NOTE PN INNER JOIN public.NOTE_DATA ND ON PN.NOTE_ID =
> ND.NOTE_ID WHERE (TARGET_PARTY_ID = ?) ORDER BY NOTE_DATE_TIME DESC (ERROR:
> column "target_party_id" does not exist)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
