Trying to find a neat solution for this myself. Post is a year old, but I think it's still very relevant. Currently I'm having to build scopes for what should really be the norm. I think a default of case insensitive makes perfect sense - that's the way it is for MYSQL, so having a simple config switch would stop a lot of headaches for Heroku users and still make it possible to switch off if someone wants case sensitive (though I can't see a situation where you'd want to globally be case sensitive with searches, they would be one off specifics only in reality). Could we get this in to v2.0pre....?
Anthony. On Thursday, 8 September 2011 22:30:29 UTC+1, Jim Harvey wrote: > > @Matt, @kevin - thanks for the feedback! really really helpful. You saved > me from adding another field to store a lowercase name, which I was about > to do and which would have been a *really* hacky mess. Custom scopes are > great now I realize that I can do that (even though I've read the docs, it > didn't sink in.) However, in this case, the search scope works perfectly. > > As far as configuration options, I would argue for field-level since it > provides the most flexibility. I can see Kevin's point about the common > sqlite to heroku dev pattern but I'm not sure you'd want to override > behavior that might be expected by experienced postgres users. > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/hobousers/-/2xs9xmSyP90J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
