I agree with phillip suggstion.
Don't go with steroids as it has limitations for multiple taggings like
tags, skills, interests ) that were extended in acts_as_taggable_on
Ruby on Rails Developer
Thanks for the suggestions guys. We already have some tagging in place,
using machine tags to delineate different kinds of tagging, eg
"note:name=Eb", so i think we would stick with that system. Maybe
that's how acts_as_taggable_on does it under the hood? Anyway i'll look
It doesn't. Here's the migrations... It uses the 'context' field.
create_table :tags do |t|
t.column :name, :string
create_table :taggings do |t|
t.column :tag_id, :integer
t.column :taggable_id, :integer
t.column :tagger_id, :integer
t.column :tagger_type, :string
# You should make sure that the column created is
# long enough to store the required class names.
t.column :taggable_type, :string, :limit => 32
t.column :context, :string, :limit => 32
t.column :created_at, :datetime