Even if you work with an ORM instead of writing raw SQL you should know when sin... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		NumberCruncher on June 25, 2017 \| parent \| context \| favorite \| on: Literate SQL Even if you work with an ORM instead of writing raw SQL you should know when single row processing is OK and when bulk load / data set processing is a must. My last employer lost 5M+ euros (not reveue but profit) every month because of excessive use of PL/SQL single row processing.

mistermann on June 25, 2017 [–]

How could they lose that much $ due to single row processing? Having to buy that much more processing power?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact