#120 ✓resolved
Jeff Judge

SQL error thrown when creating new user

Reported by Jeff Judge | November 4th, 2009 @ 02:13 PM | in 0.9.8 "Lasker"

Related to the most recent migration (023_remove_uuid.rb), I noticed the following error when trying to add new users in the admin section:

ActiveRecord::StatementInvalid (Mysql::Error: Unknown column 'uuid' in 'NEW': INSERT INTO users (company, skype, last_login_at, last_request_at, updated_at, title, perishable_token, current_login_ip, deleted_at, username, yahoo, password_salt, current_login_at, admin, aim, suspended_at, mobile, phone, google, password_hash, persistence_token, login_count, first_name, last_name, email, alt_email, last_login_ip, created_at) VALUES('', NULL, NULL, NULL, '2009-11-04 22:12:23', '', 'OcaOjzdBBg_mdaYZnYJU', NULL, NULL, 'test', NULL, 'TQfcSzyrGxwtPnrR7eZd', NULL, 0, NULL, NULL, NULL, NULL, NULL, 'fbb2884506e30f4c52bfc8f396140b50ee25d2fa2f7fac5451524f1a34d7df952839e59e77de68fd589e1ff26781b007ad9964cd26172050551da42dc6cb97c3', 'ff32c2dd6fea1392301dad0be47185b00aa286ded6b1e35e685c96fa00852eea61fdc43f7f8dc255eefcd45efd05fa767daf4be5ed876d5583095aca291c2663', 0, '', '', 'test@test.com', NULL, NULL, '2009-11-04 22:12:23')):
app/controllers/admin/users_controller.rb:82:in create' app/controllers/admin/users_controller.rb:81:increate' vendor/plugins/haml/rails/./lib/sass/plugin/rails.rb:19:in process'

I tried to track down where the uuid is being referenced to fix the issue but cannot find a reference.

Comments and changes to this ticket

  • Mike Dvorkin

    Mike Dvorkin November 4th, 2009 @ 03:16 PM

    • State changed from “new” to “hold”
    • Milestone changed from Feature Requests to 0.9.7 "Steinitz"

    It looks like you still have MySQL triggers set up that cause this error. Please run "SHOW TRIGGERS" to see if that's the case. You might want to manually do "DROP TRIGGER IF EXISTS [table_name]_uuid;". Check out db/migrate/023_remove_uuid.rb for details on how it's done.

  • Jeff Judge

    Jeff Judge November 4th, 2009 @ 04:54 PM

    Ah! When I deploy via Capistrano, I deploy w/deploy:migrations which also includes the migrations. It looks like the migration is written to not try and drop the triggers by default. Is there a reason for that?

  • Jeff Judge

    Jeff Judge November 4th, 2009 @ 05:02 PM

    In case anyone else wants to do this manually, here's a quick reference to the drop statements:

    drop trigger accounts_uuid;
    drop trigger campaigns_uuid;
    drop trigger contacts_uuid;
    drop trigger leads_uuid;
    drop trigger opportunities_uuid;
    drop trigger tasks_uuid;
    drop trigger users_uuid;

    You can't redo the migration if the code has already been deployed (unless you remove that from the db), so it's probably just as easy to do this manually.

  • Mike Dvorkin

    Mike Dvorkin November 4th, 2009 @ 05:06 PM

    • State changed from “hold” to “resolved”

    I guess it's an oversight on my part. In 023 migration I check whether you have uuid = true in config/database.yml, but you've got FFC set up long before the "uuid" setting became available.

  • Jeff Judge

    Jeff Judge November 4th, 2009 @ 05:11 PM

    No worries! Thanks for the quick response.

  • Mike Dvorkin

    Mike Dvorkin January 12th, 2010 @ 08:51 PM

    • Milestone changed from 0.9.7 "Steinitz" to 0.9.8 "Lasker"

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Ruby on Rails CRM platform for Web 2.0 and beyond

People watching this ticket