Timeline for Postgres: How to automatically fix date/time field value out of range inside the query
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2022 at 14:54 | comment | added | sci9 | From the Public World! Yes, I can handle them in the upper layer, but I thought there was another approach to tackle them inside the query. | |
| Mar 8, 2022 at 14:48 | comment | added | Laurenz Albe | Then don't input such dates. Where do they come from? | |
| Mar 8, 2022 at 14:26 | comment | added | sci9 |
thank you for your answer, but it still treats more wisely! CAST(date_trunc('month', '2022-02-29'::timestamp) + INTERVAL '1 month' AS date) - 1 returns out of range error.
|
|
| Mar 8, 2022 at 9:31 | history | answered | Laurenz Albe | CC BY-SA 4.0 |