Ahh. Yes.
I misunderstood your question.
It is the case that the #find* methods have some magic baked into them
that aren't in the rest of the query stack. They are the highest level so
the #where and arel calls would have to reach up to get them... With the
performance hit.
... IANA core
On Sun, Jan 01, 2012 at 09:48:27PM -0500, Ken Collins wrote:
I could not find the answer to this in a few Google searches and thought I
would ask.
So when are prepared statements best leveraged in ActiveRecord's interface? I
never really noticed before, but simple condition hashes or
On Dec 28, 2011, at 5:55 AM, Jon Leighton wrote:
As a side-effect of that
implementation, this code:
SomeModel.order('foo ASC').reorder('bar DESC').order('baz ASC')
does not (as might be expected) sort the returned record by baz - the
reorder overrides all previous *and* subsequent
I am using ActionMailer to parse incoming email from gmail. I found
that multi-part emails coming from Outlook clients are encoded with
charset='Windows-1252'. After creating a mail object (see
Receiver.receive() below) each part.body has charset='UTF-8' and
defaulted_charset=true. When I grab
Hi, I'm not sure I18n namespace lookup mean but there's some
libraries (like https://github.com/nofxx/symbolize) that use nested
key in a way that I find perfectly logical, so I wonder if that
warning isn't superfluous as there might be a lot of useful ways to
leverage the AR locales that are
