Mention Rails 7.1 isolation_level config #218
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The other day I was trying Falcon for the first time on a I/O bound Rails app. While I was testing I started seeing very strange errors when doing simple DB queries (PostgreSQL), for example primary_key not found for table x. Fortunately, after some research, I realized I needed switch a new Rails 7.1 config. When I did that I was amazed to see how everything started to work just fine, and feeling grateful we have an evented web server ready to be used along with Rails (thanks 🙌).
I added the config change to the top of the docs so we make sure nobody makes the same mistake, but I'm wondering if this should be turned on automatically by falcon using a Railtie?
Types of Changes
Contribution