Re:A routine gem update ended up creating $73k worth of subs...
by cpursley on Saturday January 08, 2022 @02:27AM
(#29849480)
I guess this is a Rails thing where people treat the db as a just dumb store.
[ Parent
| on HN ]
Re:A routine gem update ended up creating $73k worth of subs...
by Nextgrid on Saturday January 08, 2022 @10:33AM
(#29852584)
Do you have any resources you can recommend about using the DB for more than just a dumb datastore?
The first thing I'd be concerned about is how do you manage changes? Code is easy to version control, deploy and roll-back. Database state and things such as triggers, stored procedures, etc, less so.
Re:A routine gem update ended up creating $73k worth of subs...
by cpursley on Wednesday January 12, 2022 @04:06PM
(#29912678)
Here's one example: https://sive.rs/pg
Re:A routine gem update ended up creating $73k worth of subs...
by guiriduro on Saturday January 08, 2022 @05:58AM
(#29850504)
Not just Rails, any webdev group without the oversight of a DBA/Architect, and a penchant for simplistic ORM (mis)use plus uncorrected opinions around 'webscale' state persistence.
Re:A routine gem update ended up creating $73k worth of subs...
by capableweb on Saturday January 08, 2022 @05:52AM
(#29850469)
I think I've used Rails seriously only once or twice in my professional life but yeah, mostly treat data-stores as just dumb stores in most projects, unless it has some special requirements.