Re: RT 4.2.7: SQL error on ticket traffic

On 09/25/2014 08:05 PM, Brian McNally wrote:
> rt3_admin=# SELECT main.* FROM Scrips main JOIN ObjectScrips
> ObjectScrips_1 ON ( ObjectScrips_1.Scrip = main.id ) JOIN
> ScripConditions ScripConditions_2 ON ( ScripConditions_2.id =
> main.ScripCondition ) WHERE (ObjectScrips_1.ObjectId = '3' OR
> ObjectScrips_1.ObjectId = '0') AND (ObjectScrips_1.Stage =
> 'TransactionCreate') AND (ScripConditions_2.ApplicableTransTypes LIKE
> '%Create%' OR ScripConditions_2.ApplicableTransTypes LIKE '%Any%') AND
> (main.Disabled = '0') GROUP BY main.id ORDER BY
> MIN(ObjectScrips_1.SortOrder) ASC
> rt3_admin-# ;
> ERROR: column "main.description" must appear in the GROUP BY clause or
> be used in an aggregate function
> LINE 1: SELECT main.* FROM Scrips main JOIN ObjectScrips ObjectScrip...

That statement works just fine for me on a clean RT 4.2.7 database with
Pg 9.3.5.  I suspect something is odd with your Postgres database or
configuration -- this is likely relevant to your other thread as well.

> What's confusing is that I also upgraded another RT instance using the
> same procedure and I do not have this same issue (the SQL query above
> and ticket updates work fine).

Compare your Pg configurations.
 - Alex
-- 
RT Training - November 4-5 Los Angeles
http://bestpractical.com/training