Timeline for postgresql - Policy to prevent a field from being updated
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2023 at 22:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 15, 2023 at 4:55 | comment | added | Jonathan | I wrote an article on this after lots of research - code.build/p/XUPzns9ykZj4Abcazg1kt5/… | |
| Feb 14, 2023 at 20:14 | answer | added | tanius | timeline score: 6 | |
| Feb 7, 2022 at 13:07 | comment | added | Jonathan | ok, so it is impossible without a trigger I suppose. Thanks! | |
| Feb 7, 2022 at 7:57 | comment | added | user1822 | "as long as there is no created_at coming into the UPDATE fields." - there is no way to detect if a specific column was specified in the UPDATE statement or not | |
| Feb 7, 2022 at 5:41 | history | asked | Jonathan | CC BY-SA 4.0 |