You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.
I notice that u do separate database calls for the results?
Any reason for it?
I have a feeling that combining all the database-queries into one will be more efficient.
The thing is that I use soulmate for it's efficiency and no reason to slow it down in some other end..
Maybe provide a way to only get the ID:s from the results in search_by method?
The text was updated successfully, but these errors were encountered:
Makes absolute sense, strangely I did the same optimization where I am using this but I forgot to update it here in the gem. Will do so by tonight. Thanks a lot!
Hey sorry for the late fix, I had forgotten about this, busy in other things.
Do your info, I had to modify supermodel and add support for a 'where' method for a model to be able to run my tests. It's a basic implementation but works for most basic use cases. I have sent a pull request for the same, but until that is accepted we'll have to use my fork of it, i've overridden the supermodel gem with my fork in Gemfile. Will remove that once the pull request gets approved.
seattle-jim
pushed a commit
to seattle-jim/soulmate_rails
that referenced
this issue
Jun 18, 2013
I notice that u do separate database calls for the results?
Any reason for it?
I have a feeling that combining all the database-queries into one will be more efficient.
The thing is that I use soulmate for it's efficiency and no reason to slow it down in some other end..
Maybe provide a way to only get the ID:s from the results in search_by method?
The text was updated successfully, but these errors were encountered: