@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/-/1K_AB9gTneUJ. 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.
