Re: "Group By" Error with CustomFields

"Fisher, Michael (SON)" <[email protected]>
Newsgroups gmane.comp.bug-tracking.request-tracker.user
Message-ID <[email protected]>
>> Oct 16 17:40:36 helium postgres[4097]: [5-1] ERROR:  column
>> "main.name" must appear in the GROUP BY clause or be used in an
>> aggregate function at character 8
>> Oct 16 17:40:36 helium postgres[4097]: [5-2] STATEMENT: SELECT
>> main.* FROM CustomFields main JOIN ObjectCustomFields
>> ObjectCustomFields_1 ON ( ObjectCustomFields_1.CustomField =
>> main.id ) WHERE (ObjectCustomFields_1.ObjectId = '33' OR
>> ObjectCustomFields_1.ObjectId = '0') AND (main.Disabled = '0') AND
>> (main.LookupType = 'RT::Queue-RT::Ticket-RT::Transaction') GROUP BY
>> main.id ORDER BY MIN(ObjectCustomFields_1.SortOrder) ASC
>> 
>> When this fails, it seems to also prevent the Custom Fields
>> functionality from working at all, which is a bummer.
>>
>> I tried deleting everything from CustomFields, CustomFieldValues,
>> ObjectCustomFields, and ObjectCustomFieldValues, but this didn’t
>> help.
>>
>> Environment: FreeBSD 9.3 (migrating to 10.3), PostgreSQL 9.1
>> (migrating to 9.5), RT 4.0.24 (migrating to 4.4.1).
>> 
> Have a look at the perl SearchBuilder component, it might be that your
> fresh build has the latest with some adjustments to prevent the error
> that is thrown in your current env.

Joop,

Thanks for the tip. However, both systems show the error and both
systems are running DBIx-SearchBuilder 1.66 (current in FreeBSD
ports).

---------
RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017
smime.p7s (application/pkcs7-signature, 4.3 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.