Piero Dotti

@brendon @swanandp I confirm that using a lock on the article solves the issue. 👍 I'm not sure of it, but... shouldn't this be something that the gem could manage...

@seuros yep, it's that one! I think it could make sense to add also `suffix`, not only `prefix` :)

@seuros I agree! And what about something like: `wild: :full`, `wild: :starting`, `wild: :ending` or something like that? Maybe it's not very elegant, but all both are wildcards, aren't they?

Uhm... and what about `starting_with` and `ending_with`?

Uhm... I don't think I got how you'd like to implement it.

Oooh yes, of curse :D I left that syntax after your last message ;) What I don't understand is: how do you want to implement starting_with with parameters? ``` User.tagged_with("my,...

I don't like it very much... :\ In that way you can't do something like this: ``` User.tagged_with("my, list, of, tags", any: true, starting: true, order_by_matching_tag_count: true) ```

Mh, in that way it's pretty cool. For coherency should we change also tagged_with? Isn't it a breaking change?

oh, interesting, I like it! Do you have an idea on how to implement this feature?

If we want to keep the actual structure we can have an internal `QueryBuilder` class: ``` ruby class QueryBuilder def initialize(parent) @parent = parent ... end def order_by_matching_tag_count @order