similar to: Help needed on STI syntax

Hi everyone, I have 3 types of people (for now): Staff Faculty Students To break them up into classes, but keep them in the same People table, I''ve broken them up like so (code and ''ends'' snipped): class Person < ActiveRecord::Base class Employee < Person class Staff < Employee class Faculty < Employee class Student < Employee So, when I insert

Hi, My application has a table of People that has information about them, and I want to have a subset of those people as Users - people that can login to the application. What is the best way to do this? Add columns to People that only Users would use? I''ve read the threads on single table inheritance, but it seemed a little bit wasteful: 10,000 people vs 50 users For those more

Yeah I''m getting major problems as well. I don''t know what the issue is but I''m thinking of going back to 1.0 I would really like to hear if you figure this out, kind of an important part of Rails for us. -Paul -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hey gang, How does STI work with HABTM? For instance...let''s say I have the following models ----- Category < ActiveRecord::Base Item < ActiveRecord::Base Product < Item Deal < Item ----- Each product or deal can have categories. Would I then setup Item with has_and_belongs_to_many :categories, then create a table categories_items ??? Is there a better way to do it?

I''m currently coding a system which must store multiple contact methods for a user (phone, email, postal address etc). I''m planning a fairly straightforward inheritance hierachy for these, where each different method inherits from something like a ContactMethod class. The only mention of ActiveRecord support for inheritance I can find in the Wiki and the Agile Web Dev book is

With the help of the Rails Recipes have got a self-referential HABTM relationship working, but I''m really struggling with getting a new entry from a form accepted. i should say here that the form is also submitting info for the join table too. So in my model I have: class Type < ActiveRecord::Base has_and_belongs_to_many :subtypes, :class_name => ''Type'',

Consider the following: -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to

Guys, I have a relationship between model classes that I believe is best represented by inheritance, but the likelihood that things will change often is driving us to composition instead. So, I have a class called Autos, and subclasses called Suvs, Minis, Mids, Sports, for example. We have been requested to avoid the STI approach to this, because of fear of a quickly growing table with

I have some classes in my model which use STI and they work as expected in the console. However, when I try to use them in a migration, I get "uninitialized constant OfficePhone", for example. Why doesn''t the migration environment pick up the class defs? OfficePhone is defined in the model/phone.rb. I put model :phone in the application.rb but my migration just

Hello, I have set up that uses single table inheritance. I have a number of model subclasses following the example in AWDWR that uses Manager < Employee < Person. First question. Do I need to create controller classes for each? I don''t think I do because a single controller should be able to shunt the data between the models and the views. Second question. Say I have a view

OK. Here''s another one on STI (thanks for the help of all of you with my previous STI question, and I promise to update the wiki with the info). I''m having a prob with validation with the sub-classes. It''s a bit long-winded to explain, but I''ll post all the logs and code if there''s no obvious answers. Basically, however, I have validation on the

With the help of several heroes here yesterday I beat my way into a working solution to adding comments to one or more models in my application using acts_as_comentable. Great plugin, but my implementation is lame. I need enlightenment. I have users who log in. For several views I want to let them add comments. Enter act_as_commentable which does just this -- it''s polymorphic, so you

Having problems with STI. Names below have been changed to protect the innocent. Imagine a system that allows someone to apply for one of two different types of school scholarships. Each scholarship goes through a different review process, represented by a state machine (this is not a state machine question). So there are two state machine classes that differ slightly and subclass a generic

So this new STI :through thing is still not clear to me. I have a project now where I''m using this: class List < ActiveRecord::Base belongs_to :user end class StaticList < List has_and_belongs_to_many :items end In the script/console: >> StaticList.create NameError: uninitialized constant StaticList What? ok, fine. So a List.create would be in

Hi everyone! I have a question: what is the preferred way (in terms of simplicity) to test models with single table inheritance. Right now I have 1 test case and 1 fixture for all of the STI models, but it''s very hard to maintain it (too many tests and records in fixture). It would be better if fixtures could be named separately from DB tables. I know, Engines plugin has

I have a STI class tree. I want to set some default values (calculated values so I can''t set it in the database as defaults) on every created instance regardless of what subclass is actually instantiated. So I figured adding a after_create callback in the top class in the hierarchy should do the trick. It seems it doesn''t get called :( Code: class SuperClass <

Hello, I''m creating my own Tumblr [tumblr.com] like rails app. It''s like a blog, but in this case a blog post could be of a certain type, i.e. a regular post, a video, a link, a photo, a song(info). Well now, it''s clear that they share a lot of similar functionality: title, created_at/updated_at, commentable, probably has an author_id, etc.. But besides that they are

Hi, This does not seem to be covered anywhere. Since base class extends ActiveRecord with a table that has fields for all heirs, would that mean that any heir class can access any of those attributes, including ones that belong to other heirs? Or I am missing something? -- Posted via http://www.ruby-forum.com/.

Apologies for such a basic question. I''ve wracked my brain on this a couple days so if anyone takes pity, please help me out. I''ve been looking at STI (Single Table Inheritance) at the Rails Wiki and decided to try it out. I got it working in the model and controllers but can''t figure out how to make a proper view that will take the values and add them into the

Hi: I''m trying to create a drop-down list to change the type of a Single Table Inheritance class. I tried this: <%= select :user, :type, [ [''Author'', ''Author''], [''Editor'', ''Editor''], [''Administrator'', ''Administrator''] ]