|
Issue
|
Reported by a community member.
As with the previous two issues that I reported, when using Oracle clicking on the Maintain Users link in the admin section of Centric, you will get an "ORA-00918: column ambiguously defined" error.
The solution to this is to modify the UserList.buildList() function as follows:
@@ -1502,7 +1502,7 @@ "a.last_ip, a.timezone, a.startofday AS access_startofday, " + "a.endofday AS access_endofday, a.expires, a.alias, " + "a.contact_id AS contact_id_link, a.user_id AS access_user_id, " + - "a.enabled AS access_enabled, a.assistant, " + + "a.enabled AS access_enabled, " + "a.entered AS access_entered, a.enteredby AS access_enteredby, " + "a.modified AS access_modified, a.modifiedby AS access_modifiedby, " + "a.currency, a.\"language\", a.webdav_password, a.hidden, a.allow_webdav_access, a.allow_httpapi_access, " + @@ -1512,8 +1512,7 @@ "b.description AS site_id_name, " + "lind.description AS industry_name, " + "lcs.description AS source_name, " + - "lcr.description AS rating_name, " + - "o.name AS org_name, o.enabled AS orgenabled " + + "lcr.description AS rating_name " + "FROM \"access\" a " + "LEFT JOIN contact c ON (a.contact_id = c.contact_id) " + "LEFT JOIN lookup_industry lind ON (c.industry_temp_code = lind.code) " +
This is a problem on Oracle because the whole select statement gets wrapped in a seperate statement such as:
SELECT * FROM (...) WHERE ROWNUM < 10
where ... represents the original statement. Because there are identically named columns from several tables in the original statement in this case, Oracle cannot deal with them and barfs out an error. My solution removes the duplicate named columns.
Could someone with access to the ticketing system please raise this with the development team so that it can get corrected in core.
Cheers, Primoz
|