<h1>Extending Goldberg::User</h1>
<h2>The Problem</h2>
<p>Goldberg’s User model comes with a basic set of fields: username, password, email, name, etc. But what if you need more fields ?</p>
<h2>The Solution</h2>
<p>Create a new model in your application called ‘MyUser’ with all your required fields, and link it to ‘Goldberg::User’</p>
<p>You could also modify Goldberg::User directly, but that is not recommended as you would also need to add more columns to the goldberg_users table, which could complicate upgrades. Remember, Goldberg is a plugin; don’t mess with your plugin’s tables.</p>
<h2>The Code</h2>
<pre><code># put this in your app/models/myuser.rb
Goldberg::User.class_eval do
has_one :myuser
end
class Myuser < ActiveRecord::Base
belongs_to :user, :class_name => 'Goldberg::User', :foreign_key => 'goldberg_user_id'
# other associations
# example: has_many :posts
end</code></pre>
<h2>Migration</h2>
<p>Add a <strong>goldberg_user_id</strong> foreign key field to <strong>myusers</strong> table.</p>
<h2>Loading the Associations</h2>
<p>These associations will get loaded the first time that Rails needs to access the Myuser class; but before that Rails won’t understand what #myuser means. This could be an issue if for example you have a layout that uses “Goldberg.user.myuser.some_field_name”.</p>
<p>For that reason you might want to “require ‘myuser’” in your RAILS_ROOT/config/environment.rb.</p>
2008-07-11T21:09:11-07:00
35499
extending-goldberg-user
32863
Extending Goldberg::User
2008-07-14T20:14:02-07:00
10853