On 03/06/2013 00:51, Niels Kristian Schjødt wrote:
Hi, thanks for answering. See comments inline.
Den 05/03/2013 kl. 15.26 skrev Julien Cigar jci...@ulb.ac.be:
On 03/05/2013 15:00, Niels Kristian Schjødt wrote:
Hi,
I'm running a rails app, where I have a model called Car that has_many
On Tue, Mar 5, 2013 at 4:07 PM, Joshua D. Drake j...@commandprompt.comwrote:
On 03/05/2013 03:51 PM, Niels Kristian Schjødt wrote:
3ms isn't slow
Sorry, it's 3323ms!
Can I do anything to optimize that query or maybe the index or something?
your index is already used
Okay this
Hi,
I'm running a rails app, where I have a model called Car that has_many Images.
Now when I tell rails to include those images, when querying say 50 cars, then
it often decides to use a SELECT * from images WHERE car_id IN
(id1,id2,id3,id4…) instead of doing a join.
Now either way it uses
On 03/05/2013 15:00, Niels Kristian Schjødt wrote:
Hi,
I'm running a rails app, where I have a model called Car that has_many Images.
Now when I tell rails to include those images, when querying say 50 cars, then
it often decides to use a SELECT * from images WHERE car_id IN
Hi, thanks for answering. See comments inline.
Den 05/03/2013 kl. 15.26 skrev Julien Cigar jci...@ulb.ac.be:
On 03/05/2013 15:00, Niels Kristian Schjødt wrote:
Hi,
I'm running a rails app, where I have a model called Car that has_many
Images. Now when I tell rails to include those images,
On 03/05/2013 03:51 PM, Niels Kristian Schjødt wrote:
3ms isn't slow
Sorry, it's 3323ms!
Can I do anything to optimize that query or maybe the index or something?
your index is already used
Okay this leaves me with - get better hardware or?
What does explain analyze say versus just