Skip to content
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.

How to deal with case sensitivity varying depending on rdbms used? #237

Open
crantok opened this issue Jan 30, 2013 · 0 comments
Open

How to deal with case sensitivity varying depending on rdbms used? #237

crantok opened this issue Jan 30, 2013 · 0 comments

Comments

@crantok
Copy link

crantok commented Jan 30, 2013

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant