Viewing profile — fooododododo
fooododododo
HN member- Joined
- Thu, Dec 07, 2023, 6:22 PM UTC
- HN karma
- 3
- Public activity
- 7 items
- HN profile
- View on Hacker News ↗
About fooododododo
No profile information was provided.
Recent public activity
-
comment
Comment #42239820
Curious what your opinion on plpgsql functions is? Could easily solve your initial problem (if I follow). They don't seem to come up much though
-
comment
Comment #42239795
Do they ever write plpgsql? If not why not?
-
comment
Comment #42097214
Is everything in pgdump in the information schema?
-
comment
Comment #39869235
Why not run Pg in a container if that's what's in prod?
-
comment
Comment #38573403
Agree re trigger maintenance Re orm, I'm strongly biased towards only using them when they (1) are absolutely necessary or provide some extreme benefit (2) are able to output the r…
-
comment
Comment #38570089
Seems like a rant rather than a comment to the post? Timescale has continuous aggregates that might be interesting, writing a table built by a trigger isn't hard, and some might sa…
-
comment
Comment #38559853
Tracking triggers etc is pretty straightforward, just put them in a repo and apply them as part of a schema change. Testing them can be tricky, as unit tests aren't as likely to ca…