15 Jun '13, 8am

@checker Have a look at the official Rails guides for how to do joins:

But this approach becomes increasingly impractical as the table size increases, since User.all.each instructs Active Record to fetch the entire table in a single pass, build a model object per row, and then keep the entire array of model objects in memory. Indeed, if we have a large number of records, the entire collection may exceed the amount of memory available.

Full article: http://guides.rubyonrails.org/active_record_querying.html...

Tweets

#MIPI interface finds use in medical and automotive applications

#MIPI interface finds use in medical and automo...

newelectronics.co.uk 16 Jun '13, 7am

The Alliance's task was to standardise the chip interfaces used within handsets and, in particular, to develop interfaces ...

First Look: details about #LEED v4 reference guides:

First Look: details about #LEED v4 reference gu...

usgbc.org 12 Jun '13, 1am

Quick - what’s the first thing that comes to mind when you want to understand a credit? The reference guide. It's like the...

Active Record batch processing in parallel proc...

m.onkey.org 08 Jun '13, 10pm

Active Record batch processing in parallel processes Published almost 2 years ago Active Record provides find_each for bat...

Learn Ruby on Rails

sitepoint.com 14 Jun '13, 7am

Ruby on Rails is the web development framework of the moment, powering Gitub, Twitter, Hulu and many more successful apps ...

tutorial "User Authentication with Rails, RSpec...

larsgebhardt.de 14 Jun '13, 8pm

It handles multiple functions. At first we use the rails helper functions to find a a user with the entered email and pass...