So I know STI is the most reviled thing ever but I have an instance where I think it might actually make sense.My app is parsing a bunch of different types of xml files.Every file model stores the exa
I have an ActiveRecord model Media which is supposed to be able to store similarly structured information about different types of media (Media::Book, Media::Movie, Media::Music). However each of thes
I am implementing a web solution with rails 3 where a user has a list of \"Actions\". They can either be pending or validated and only an admin can validate.
I am working on a project (Rails 3.0.3) where I think I may need to use STI, but I am not sure if I should just add an extra column to a table and be done with it.
For my project management application, I am currently using Single Table Inheritance so that: Lead < Requirement
My app has an STI model: 开发者_高级运维# file: app/models/metered_service.rb class MeteredService < ActiveRecord::Base
I am working with a code base that has this single table inheritance hierarchy: BlogEntryWizardController < BlogEntriesController < CommonEntryController < ApplicationController
I\'ve got a super-class (model) Measurement and two sub-classes: WeightMeasurement and LengthMeasurement.
I need to be able to schedule reminders for users. So I thought I could just create a base model Reminder and use STI to make descendant classes which override the function fire(), called when reminde
I\'ve come across this rather odd bit of behaviour in a rails application I\'m working on. I have multiple types of Post in an inheritance heirarchy, and a Post has_many FeedEntries.
加载中,请稍侯......