Fix to ::Sequel::Dataset.class_eval when doing raw query #1
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.
I'm using Sequel in my rails project indirectly and not inheriting from Sequel::Model. Thus I was crashing since I didn't have model defined. I changed the code to add defined?(model) but then I didn't have first_source defined (because again I'm doing raw queries). So I changed it to return the raw SQL query by calling the sql method. This might not be desirable in the default case but since my SQL queries weren't getting connected to the results page, it was the only way to know what was going on.
If you want to test my use case simply define a model like this: