Rails and shitty SQL generation

Chris — Wed, 27 Feb 2008 20:57:00 -0600

Just a quick bitch about something I came across in setting up Redmine.

Removing members from a project in the admin interface was silently failing for me.

It turns out that Redmine, rather sensibly, updates the project so that no issues are automatically assigned to the user being removed from the project. This makes a call to ActiveRecord::Base’s update_all method.

This was the call that was failing, and it was all down to the fact that ActiveRecord was passing my postgres database an update query with an “ORDER BY” clause, which is apparently the sort of fucking retarded feature that mysql decided to implement, and which some useless dick chose to support in AR.

Really, what’s the point of ordering your update statement?

I don’t know who to be more pissed off at over this, but given past experiences with mysql I’ll pin it on them.

FUCK YOU AGAIN, MYSQL!

"Rails and shitty SQL generation" by Matt Wilson

Thu, 22 May 2008 10:24:18 -0500

Yeah, AR can do some really gnarly stuff. You ever get frustrated when it makes 40 separate queries instead of a single query with a join?

I heart redmine though.

Drinkingbird: Rails and shitty SQL generation

Rails and shitty SQL generation

"Rails and shitty SQL generation" by Matt Wilson