I was just faced with a strange ROLLBACK exception when attempting to
execute this code:
$ rails console
user = User.first
User Load (1.1ms) SELECT "users".* FROM "users" ORDER BY
"users"."id" ASC LIMIT 1
=> #<User id: 1, name: "Michael Hartl", email: "f...@bar.com",
created_at: "2013-05-12 12:47:23", updated_at: "2013-05-12 13:24:26",
password_digest: "$2a
$10$CYZFddDa5Glv0dlYhlpZguIuzfyMRiwleaenmh67hFyK...">
irb(main):005:0> user.update_attributes(email:
'exam...@railstutorial.org')
(2.1ms) BEGIN
User Exists (4.2ms) SELECT 1 AS one FROM "users" WHERE
(LOWER("users"."email") = LOWER('exam...@railstutorial.org') AND
"users"."id" != 1) LIMIT 1
(0.7ms) ROLLBACK
=> false
There definitely is no user in the database (Postgres) matching given
email.
blog=> \d users
Table "public.users"
Column | Type |
Modifiers
-----------------+-----------------------------
+----------------------------------------------------
id | integer | not null default
nextval('users_id_seq'::regclass)
name | character varying(255) |
email | character varying(255) |
created_at | timestamp without time zone |
updated_at | timestamp without time zone |
password_digest | character varying(255) |
Indexes:
"users_pkey" PRIMARY KEY, btree (id)
"index_users_on_email" UNIQUE, btree (email)
The strange thing is that listing most of the fields in the update
works (as instructed in the tutorial
http://ruby.railstutorial.org/chapters/sign-up?version=4.0#top
in the section of adding Gravatar).
irb(main):007:0> user.update_attributes(name: 'Example User', email:
'exam...@railstutorial.org', password: 'foobar',
password_confirmation: 'foobar')
(3.0ms) BEGIN
User Exists (0.9ms) SELECT 1 AS one FROM "users" WHERE
(LOWER("users"."email") = LOWER('exam...@railstutorial.org') AND
"users"."id" != 1) LIMIT 1
SQL (133.5ms) UPDATE "users" SET "name" = $1, "email" = $2,
"password_digest" = $3, "updated_at" = $4 WHERE "users"."id" = 1
[["name", "Example User"], ["email", "exam...@railstutorial.org"],
["password_digest", "$2a
$10$0i9ihaDD9nU6QxiGNiKEGeIarY9faPWY9lAAlLIzYz8UMyyz7R/mW"],
["updated_at", Sun, 19 May 2013 07:55:25 UTC +00:00]]
(0.6ms) COMMIT
how come? What connection do other fields bear with the ability to
save the model?
Here's the model:
class User < ActiveRecord::Base
before_save { email.downcase! }
validates :name, presence: true, length: { maximum: 50 }
validates :email, presence: true,
format: { with: /\A[\w+\-.]+@[a-z\d\-.]+\.[a-z]+\z/
i },
uniqueness: { case_sensitive: false }
has_secure_password
validates :password_confirmation, presence: true
validates :password, length: { minimum: 6 }
end
Rails 4.0.0.beta1, Ruby ruby-2.0.0.0, ruby20-gems-1.8.25
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-talk+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
