From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | Peter Childs <peterachilds(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: delete from a using b in postgres 8.1. |
Date: | 2006-01-03 19:18:51 |
Message-ID: | c2d9e70e0601031118t7e8dbd85m3da826d0b845644@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 1/2/06, Peter Childs <peterachilds(at)gmail(dot)com> wrote:
> a command such as
>
> delete from a using b where a.one=b.one and b.two='foo';
>
> works fine in 8.1 but fails totally in 8.0 however
>
> delete from a where a.one=b.one and b.two='foo';
>
> works fine in 8.0 and bellow but fails in 8.1 unless you have the
> add_missing_from option set to true in 8.1
> Even then it produces a nasty warning.
>
it will not break anything because you can set this flag in the
VERSION/PLATFORM COMPATIBILITY section of postgresql.conf
> This can break tones of clients admittedly the work around is quick but not
> particularly neat. What do the other sql database do and is this just
> another inconstancy in SQL?
>
> I realise this was done to fix a bug but its a nasty sitting there that many
> client developers are going to miss it before it goes back to the end user.
> I also don't think this has been made particularly clear in changes.
>
> Peter Childs
>
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Tenenbaum | 2006-01-03 22:15:25 | getting a query column to return 0 if nothing matches |
Previous Message | Peter Childs | 2006-01-02 13:28:30 | delete from a using b in postgres 8.1. |