-
Notifications
You must be signed in to change notification settings - Fork 565
Fix issue with default view value not being found because of case sensitivity #1113
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
Conversation
|
@budiljak Could you review this please? |
budiljak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can hardly judge the code changes as I don't know the details of module. But I checked it out and it seems to work for the boolean field.
BUT I just tried it with a default value for a string and that doesn't work. Should I open another issue for that or is this related to that fix here?
|
Probably related. Could you add a script that shows the issue for a default value for a string? |
|
Here it is: |
|
Remark: It's not about case sensitivity here. |
|
@budiljak The issue with the default string value seems to be a separate issue. It happens in previous versions of the gem before v7.0.4.0. Would you mind opening it as a separate issue and include that script you have above. Thanks |
budiljak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok.
Fix for #1099
The issue was caused by case sensitivity when finding a view column's default value following #1073
This PR downcases the column names involved so casing is no longer relevant.