CODEWITHSUNDEEP
ruby-on-railsactiverecordruby-on-rails-3.2
jibiel
jibiel

Reputation: 8303

ActiveRecord::Querying#first returns third member of the collection

[1] pry(main)> User.first
  User Load (0.4ms)  SELECT "users".* FROM "users" LIMIT 1
=> #<User id: 3, email: "[email protected]", encrypted_password: "$2a$10$lqsgKvQuz9iSIu/..FMRJu76H9KNhfVz5x9DmxphC0TK...", reset_password_token: ... >
[2] pry(main)> User.find(1)
  User Load (12.8ms)  SELECT "users".* FROM "users" WHERE "users"."id" = $1 LIMIT 1  [["id", 1]]
=> #<User id: 1, email: "[email protected]", encrypted_password: "$2a$10$pGDcv0/EgiDk4KcZN9pli.evx5Ni1qOoujQD15HgWH8Y...", reset_password_token: ... >
[3] pry(main)> Product.first
  Product Load (0.6ms)  SELECT "products".* FROM "products" LIMIT 1
=> #<Product id: 1, name: "Ruby on Rails Jr. Spaghetti", created_at: "2012-01-25 10:13:26", updated_at: "2012-01-25 10:13:26", properties: ...>

This is happening in the console and during runtime and only for the User model. What could cause such behaviour?

Upvotes: 1

Views: 148

Answers (2)

Baldrick
Baldrick

Reputation: 24340

User.first is the same as User.all.first, there is no specified order, so the DB returns the list of element in any order. If you want to get the User with smallest id, use User.order("id").first.

If your request returns several elements and you want to pick any of them, you may want to use first without specified order.

Upvotes: 1

Frederick Cheung
Frederick Cheung

Reputation: 84114

You haven't specified an order - the database is free to order the results in any way it wants. It could be primary key order, it could be how things are laid out on disc but without an order clause there are no guarantees.

If you want the first record in a specific order, then make sure you ask for it

Upvotes: 5

Related Questions