You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
I just experienced a behaviour difference between my development and staging apps and would like to know whether I can change this.
I am (probably inadvisedly) using different rdbms on development (sqlite) and staging (mysql). Retrieving a row using the following code
User.first(login: params[:to])
where login is a string, returned nil with sqlite and a valid User object with mysql. In both cases, the search string params[:to] was incorrectly cased.
Is there any way to
specifiy case-sensitivity at comparison, or
specify case-sensitivity at table creation, or
specify case-sensitivity globally?
I saw issue #97 but as that was two years ago so I thought I'd just check.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I just experienced a behaviour difference between my development and staging apps and would like to know whether I can change this.
I am (probably inadvisedly) using different rdbms on development (sqlite) and staging (mysql). Retrieving a row using the following code
where login is a string, returned
nil
with sqlite and a validUser
object with mysql. In both cases, the search stringparams[:to]
was incorrectly cased.Is there any way to
I saw issue #97 but as that was two years ago so I thought I'd just check.
The text was updated successfully, but these errors were encountered: