Re: weirdness with the a sql update
От
Douglas McNaught
Тема
Re: weirdness with the a sql update
Дата
Msg-id
m2fytplq73.fsf@Douglas-McNaughts-Powerbook.local
Ответ на
weirdness with the a sql update (Tony Caduto)
Список
Дерево обсуждения
pgsql-odbc list problem "Alejandro D. Burne" <alejandro.dburne@gmail.com>
Re: pgsql-odbc list problem Richard Huxton <dev@archonet.com>
Re: pgsql-odbc list problem "Alejandro D. Burne" <alejandro.dburne@gmail.com>
weirdness with the a sql update Tony Caduto <tony_caduto@amsoftwaredesign.com>
Re: weirdness with the a sql update Sven Willenberger <sven@dmv.com>
Re: weirdness with the a sql update Martijn van Oosterhout <kleptog@svana.org>
Re: weirdness with the a sql update Michael Fuhr <mike@fuhr.org>
Re: weirdness with a sql update Tony Caduto <tony_caduto@amsoftwaredesign.com>
Re: weirdness with the a sql update Douglas McNaught <doug@mcnaught.org>
Tony Caduto writes: > Hi, > > I just noticed this, if I do a update like this: > > update new_requests set name = 'tony' where request_id = 2 > > If I do a select * from new_requests that record I just updated is now > at the bottom , before the update it was at the top? > > Why is Postgresql changing the ordering of the results after a simple > update? Results are returned in an arbitrary order unless you supply an ORDER BY clause in your query. > It almost looks like the record is being dropped and then readded to > the end. Yup. In Postgres, UPDATE == DELETE + INSERT, so the new row will very likely go into a different place (this is so that existing transactions can still see the old row before your transaction commits). -Doug
В списке pgsql-general по дате отправления