pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
delete from a using b in postgres 8.1. 2+ messages / 2 participants [nested] [flat]
* delete from a using b in postgres 8.1. @ 2006-01-02 13:28 Peter Childs <peterachilds@gmail.com> 2006-01-03 19:18 ` Re: delete from a using b in postgres 8.1. Jaime Casanova <systemguards@gmail.com> 0 siblings, 1 reply; 2+ messages in thread From: Peter Childs @ 2006-01-02 13:28 UTC (permalink / raw) To: pgsql-sql 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. 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: delete from a using b in postgres 8.1. 2006-01-02 13:28 delete from a using b in postgres 8.1. Peter Childs <peterachilds@gmail.com> @ 2006-01-03 19:18 ` Jaime Casanova <systemguards@gmail.com> 0 siblings, 0 replies; 2+ messages in thread From: Jaime Casanova @ 2006-01-03 19:18 UTC (permalink / raw) To: Peter Childs <peterachilds@gmail.com>; +Cc: pgsql-sql On 1/2/06, Peter Childs <peterachilds@gmail.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 ;) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2006-01-03 19:18 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2006-01-02 13:28 delete from a using b in postgres 8.1. Peter Childs <peterachilds@gmail.com> 2006-01-03 19:18 ` Jaime Casanova <systemguards@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox