Timeline for How to force order of WHERE clauses in PostgreSQL?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 2, 2018 at 22:22 | history | bounty ended | ypercubeᵀᴹ | ||
| Aug 27, 2017 at 1:53 | comment | added | Erwin Brandstetter |
Adding a final SELECT to return a row with default(s) is totally optional. If defaults come from another query, it can save another round trip to the DB server, though.
|
|
| Aug 25, 2017 at 8:53 | comment | added | Sławomir Lenart |
no need adding default value here, no rows is a valuable as well and can be easily handled when operating on the result (a programmer's point of view)
|
|
| Aug 25, 2017 at 8:37 | vote | accept | Sławomir Lenart | ||
| Aug 25, 2017 at 0:38 | history | edited | Erwin Brandstetter | CC BY-SA 3.0 |
added 2 characters in body
|
| Aug 25, 2017 at 0:33 | history | answered | Erwin Brandstetter | CC BY-SA 3.0 |