Friday, October 27, 2017 Transactions in Ruby on Rails can be deceptively tricky to master. The following illustrates a few examples of when using simple transactions can go awry and inadvertently fail to provide atomicity. The Setup This article explores a simple app composed of surveys and questions. Surveys require a name. Questions require some text. For the examples surveys have and belong to
![Transactions in Ruby on Rails and Atomic Bugs](https://cdn-ak-scissors.b.st-hatena.com/image/square/71492a421934ebffe638da2f00aa0893feda83cf/height=288;version=1;width=512/https%3A%2F%2Fksylvest.com%2Fassets%2Fprofile%2Fdefault-5babf7464197c2c9ae8d4e9333d375de59ba03fb25f109e11d6f7e9ea39858bb.jpg)