4 ms·

> I think most apps will need a transaction involving more than 25 rows at some point I ... can't think of a single time I've ever needed this.

• danenania 6y ago
  A common one is cascading deletes when you delete a user or a ‘project’ or something else that has a lot of stuff associated with it. Those will exceed 25 rows very quickly. Also any kind of bulk update or data import... hell even just initializing a new account can easily require writing more than 25 rows in a moderately complex app.
  • the_reformation 6y ago
    Still, why the need to be transactional? An eventually consistent delete seems fine here.
    • danenania 6y ago
      Maybe it is, or maybe some of the rows are involved in a security check. Or could cause race conditions if out of sync. Or otherwise need immediate read-after-write consistency. And eventually consistent isn't the worst case scenario. Being unable to rollback correctly from an error could mean you'll never end up in a consistent state... that's a lot worse than "eventually".
• kulig 6y ago
  Youve never worked on a minimally complex enterprise application?