#354 Squeel

Thanks Ryan.

This is good if all database drivers support it. Otherwise we'll have the same issue as using plain old SQL.

IMHO, unless something like this is adopted by Rails out of the box, the prons and cons of using a gem with another DSL almost even.

I have a gist integrating Squeel with CanCan ( https://gist.github.com/1523940 ) that lets one do outer joins and less common operations:

# example domain names: domain.com, sub.domain.com

# in ability
can :manage, Domain, :permissions.outer => {:user_id => user.id}
can :manage, Domain, :name_reversed.matches => "#{domain.name_reversed}.%" # descendants

# in controller
@domains = Domain.accessible_by(current_ability) # or
authorize! :read, @domain

Hope Ryan will integrate it soon.

We use Squeel on all of our projects and it totally rocks. It's a really pretty little DSL.

Nice bit to know about calling "my" to get the original context.
I'd started creating variables before the where clause so I could call them, I think "my" is better.

Love Squeel. Love that I don't have to mess with ARel.

I've used Squeel exclusively for developing my tagging library. Compared to acts as taggable on steriods the code is very readable.

https://github.com/bradphelan/rocket_tag

It makes writing composable SQL a breeze.

I love Ernie Miller's two main projects (Squeel & Ransack / previously metawhere & metasearch).
As much as Squeel cleans up DB look ups, I find Ransack totally brilliant, it makes standard (and you can go quite sophisticated) searches in indexes so easy and flexible!

What are the performance concerns with using Squeel?

We recently removed Metawhere from our Rails 3.0.x app and our specs complete around 5X faster.

What's about Sequel? README CheatSheet

What is better Squeel or sequel?

Does Squeel support hstore?

Is there a good way to implement this functionality?

I got this working great in the rails console, right off the bat. Fell in love immediately. Then when I implemented it in the views I kept getting "wrong number of arguments 0 for 1". Googling around I found I wasn't the only one, lots of people were getting that error and I couldn't really find a strait answer.

Eventually I restarted the rails session and BOOM, it works!

So
"wrong number of arguments 0 for 1" => try restarting session.

anyone have tips on creating a dynamic query with Squeel. for example if i have an array of conditions [[column,operator,value],[column,operator,value]]

How would i iterate over those and dynamically build a query in squeel?

in ultra basic format

def self.with_conditions(conditions)
    where do
        conditions.each do |column,operator,value|
            (column operator value)
        end
    end
end

I just added the squeel gem to the Gemfile in my project, did a bundle install and it installed without a problem. I then tried to use it with a very simple query like this:

InsertionOrder.where{id = 1}

in a controller and got

ArgumentError: wrong number of arguments (0 for 1+)

I tried the same query and many variations in the rails console and still got the same error.

InsertionOrder.where(id: 1) works just fine.

I saw that patrick above says restarting his session helped but it has for me on many restarts.

I've tried using several other operators and tried putting the expression in parentheses, but with no change in result.

I Tried doing the rake initialization to make the squeel.rb config file in case that would help but it didn't.

Any ideas?

@milenmaxon ORM = Object Relational Mapping, in plain language, it's a wrapper for connecting to and querying databases that is for the most part, agnostic about the choice of database.