RE: [GENERAL] changing between 6.4.1 and 6.5

1999-08-26 Thread Stuart Rison
At 8:38 am +0200 26/8/99, Jens Felber wrote: >At 18:02 25.08.99 +0200, dpeder wrote: >>have You set any triggers, rules, listens or defaults for tablex? >> > > >Nothing is set. I create a new table for tests. > > --> create table test1 (x1 int2, x2 int2, tx char); > >then I've inserted some values

RE: [GENERAL] changing between 6.4.1 and 6.5

1999-08-25 Thread Jens Felber
At 18:02 25.08.99 +0200, you wrote: >have You set any triggers, rules, listens or defaults for tablex? > Nothing is set. I create a new table for tests. --> create table test1 (x1 int2, x2 int2, tx char); then I've inserted some values: --> insert into test1 values (1,2, 'a'); --> insert in

RE: [GENERAL] changing between 6.4.1 and 6.5

1999-08-25 Thread Daniel Péder
have You set any triggers, rules, listens or defaults for tablex? -Original Message- From: Jens Felber [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, August 25, 1999 5:40 PM To: Stuart Rison; [EMAIL PROTECTED] Subject:Re: [GENERAL] changing between 6.4.1 and 6.5 At 13:02

Re: [GENERAL] changing between 6.4.1 and 6.5

1999-08-25 Thread Jens Felber
At 13:02 25.08.99 +0100, Stuart Rison wrote: >Hi, > >>realized the same error: >>ERROR: illegal use of aggregate or non-group column in target list >>(aggregates are not existing in my database) >> >>Statement: select x1, x2, x3, x4 on tablex order by x1, x2;

Re: [GENERAL] changing between 6.4.1 and 6.5

1999-08-25 Thread Stuart Rison
Hi, >after an installation of PostgrSQL v6.5 on a new machine >i have problems with a view which is running without problems >under 6.4.x. >But the view isn't the problem. The same statement on the real table >realized the same error: >ERROR: illegal use of aggregate or non-group column in target

[GENERAL] changing between 6.4.1 and 6.5

1999-08-25 Thread Jens Felber
Hi List, after an installation of PostgrSQL v6.5 on a new machine i have problems with a view which is running without problems under 6.4.x. But the view isn't the problem. The same statement on the real table realized the same error: ERROR: illegal use of aggregate or non-group column in target