Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This would also require adding the ORDER BY clause, as there might be applications where the order in which they are updated matters.


Is not any single query in Postgres a transaction? I don't think individual rows would be visible outside that transaction until all are updated.


The question is which rows would be updated by a single execution of a UPDATE...LIMIT query. The order of result rows of a SELECT query is undefined in Postgres unless you add an ORDER BY clause. It is natural to assume that an UPDATE...LIMIT would be similarly affected.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: