-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using approvals to verify_sql #91
Comments
Okay, it's taken me several passes at reading this issue to even begin to understand what this is... but I'm starting to get it, and this does indeed look very cool. It'll be a while before I'm familiar enough with this codebase to be confident in adding it, but thanks for posting your solution here! :) |
No worries either way, and of course please feel free to close this issue... since it's not really an issue! I'd be happy to document somewhere else or provide a sample app etc, I just didn't see anywhere better to share! |
Closing this as I'm doing some house cleaning, but feel free to move do a wiki, discussion, or whatever. Thank you! |
I've had good luck with the following pattern in my apps and I'm curious if there would be any interest in wrapping this up into a new feature for the gem as we have the
verify
helper. No worries in any case, but I thought I'd share the pattern here for other people to consider. I find this useful for watching the SQL that complex scopes generate. It also comes in handy when working with GraphQL to ensure that common queries generate reasonable SQL. The end result is something akin to what thebullet
gem does, but a bit more specialized, and with an easily readable record that prevents accidental N+1s etc.The text was updated successfully, but these errors were encountered: