Update readme with info on querying #238
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding some info on the new block-based interface for querying. If anyone is interested, please checkout the master branch and give this a go. I will release it in the next week or two, probably ActiveRecord alone first (not yet sure how Sequel will come out).
This will be very useful for gem integrations in particular, since it means that a gem that requires querying on translated attributes can be integrated once for all backends. This has been done already for FriendlyId without this level of granularity because querying in FriendlyId is quite simple, but most other querying gems require a more fine-grained interface. Ransack is the one I'm thinking of integrating first, since I'm sure it's one people would want.
Within Mobility, the first concrete benefit of this new querying interface is that it has enabled case insensitive uniqueness validation (which requires
LOWER
on an Arel predicate, now possible thanks to #235.