similar to: Single Table Inheritance using a boolean column

What am I doing wrong? I have a simple MySQL table: drop table if exists agencies; create table agencies ( id int not null auto_increment, type varchar(20) not null, name varchar(255) character set utf8 not null, primary key (id) ); An equally simple Model: class Agency < ActiveRecord::Base end class FotoAgency <

Please tell me if this train of thinking makes sense, I need help on solving this association model problem: I am doing an app that creates and manages stereoscopic images, one stereoscopic image is formed by two photos, say photo1 and photo2 The user uploads photo1 and then photo2 and gets a preview if he likes the preview he/she authorizes it and gets a final stereoscopic image All this

I''m having a class called Person, with subclasses as goalkeeper, forward, defender. Now a person can be a forward as well as a defender or a goalkeeper. I want to use single table inheritance like : class Goalkeepr < Person end And not have multiple boolean columns like in my people table like is is_goalkpeer, is_forward, is_defender. How do I go about it ? Thanks, Pratik -- rm

Single Table Inheritance question. class Employee is the master model (table is employees) class Cog is the subclass model, and uses single table inheritance to be a subclass of Employee class Blurfl is a normal model (table is blurfls) in cog.rb, I have something like: def foo Cog.find(:all, :include=>''blurfl'', :condition=> ["cogs.status =

Does anyone have any experience making this work? I installed the plugin and tried the following: class SomeClass < ActiveRecord::Base acts_as_Taggable end class SubClass1 < SomeClass end class SubClass2 < SomeClass end SubClass1.tag_with("tag") and notice that taggable_type = SomeClass when I do SubClass2.find_tagged_with("tag") a SubClass1 object is

So is the official stance as per edge rails that multiple class definitions must go into separate files? I was trying to use STI with acts_as_attachment, to have all my attachment classes go into a single file, for example: attachment.rb class Attachment < ActiveRecord::Base end class UserPicture < Attachment belongs_to :user, :foreign_key => ''owner_id''

Hallo, I am having a very strange Problem with STI in my application. setup: - two tables one called "wikis" on called "categories" with a hbtm relationship. - the wikis table is the sti one with a model PageWiki being extended from Wiki (and the correspondig type column) Following happens: - server restart - get :wikis, :show_pages - in show_pages the first line says

I''ve got some problems right now using the new model for relationships in fixtures (by label, not by id) and STI. What I''ve got, is a couple of models: Attachment --> FileDownload Version Version has_one file_download with file_download_id on the versions table In my fixtures, I have two FileDownloads in my attachments.yml like so: hemingway_alpha_zip: size: 100

Sorry if I''m just dumbing out, but is there a reason that when using Single Table Inheritance Rails doesn''t really validate the "type" field or provide some mechanism to do so? seems like a good way to corrupt a database. Because the "type" is also a special attribute, I had to resort to an ugly hack like: class ActiveRecord::Base def type_attr

Hi! I''ve got a subscription form in which someone can decide to give a gift to someone else. So you have to enter subscriber and recipient data in one form. For my user model I use single-table inheritance. It works fine but I''ve got a bug in the validation which I''m not able to solve. For both users, subscriber and recipient, you have to enter an email address. It is

Can someone please help me understand the results that are being produced when doing queries on a table that is using single inheritance. Table1 < ActiveRecord::Base Role1 < Table1 Role2 < Table1 Role3 < Table1 1. Role1.find(:all) produces: "SELECT * FROM table1 WHERE type = ''Role1''" 2. any other find on table1 that calls anything but the Role1 Class

FIXED: Transaction is a reserved word, and it cannot be used even though I put it into its own module. So my guess is Transactions::Transaction still somehow got resolved to the Rails internal Transaction class. Renamed the Transaction (and its subclasses) to Transact and it works fine now. Thanks! -- cmdjohnson On Sat, Jun 9, 2012 at 3:08 AM, Commander Johnson

Hi everyone, I''m working on a new rails project and have to build it on top of a legacy oracle database. I''m trying to figure out how to get the number value from a NUMBER(1) datatype. So far I''m only getting a "true" value for 1 and "false" for any other number. From the console I can print out my object values and can see that there are number

I''m trying to build a system for generically storing an object graph, on top of AR itself. The idea is to define one base class, and use AR''s automatic single table inheritance to have it create the right class. Here''s what I have so far: table generic_objects: id int(11) not null auto_increment primary key type varchar(255) table generic_fields: id

Hey all I've been running a Dovecot 1X server for awhile. Most of the config was pretty simple using flat files. I'm switching to Dovecot 2X now, and want to switch to using SQL for lookups so I can share info with the Postfix front end. For starters I setup two SIMPLE SQL tables -- a 'users' table and a 'aliases' table, where each user can have many aliases. I want to

Hi everybody I am totally new to rails and I am trying to start a tiny project to get familiar with rails. But I already got my first problem and I would be happy if somebody could point me in the best and cleanest direction. I am trying to develop a small gallery app. Since I would like to add more features in future I am trying to design a clean OO architecture of my models: The base object

Hello, I stumble upon this error when loading a subclass of the Transaction class. For full details, see the pastie: http://pastie.org/4053678 Error message: ActiveRecord::SubclassNotFound: The single-table inheritance mechanism failed to locate the subclass: ''Transactions::DummyDdnlTransaction''. This error is raised because the column ''type'' is reserved for

Hello, is it possible to setup a model/table schema like this: Groupable --> Membership <-- Group ^ ^ | | User UserGroup I tried the following but failed: Groupable (table with ''type'' column) has_many :memberships, :as => :groupable has_many :groups, :through => :memberships

I am thinking that I have found a bug in Rails migrations. My app is using UUIDtools to generate guids for primary keys. To do this I pass :id=>false and then create my own id column as shown below. Next I leverage "execute" to create an index. It seems to work fine. The table in MySql is perfect. However the ID column and primary key on the ID column are not in the schema.rb file I

Hi, I have 2 tables, "users", and "user_comments". I am trying to allow users to leave comments on each other''s profiles (eg, think youtube like this: http://www.youtube.com/profile_comment_all?user=google). Here is a simplified view of my database schema: mysql> describe users; +-----------------+--------------+------+-----+---------+----------------+ | Field