single-table-inheritance

Because of company rules I can't use our domain class names; I am going to use an analogy instead. I have a table called projects which has a column called 'type' with possible values as 'indoor' & 'outdoor'. Records having indoor and outdoor have clear functionality separation and would fit pretty neatly as a STI implementation. Unfortunately I can't change the type-names and can't add classes inside the global namespace. Is there a way to specify a different value for 'type'? Note: I am not trying to use a different column name instead of 'type' for STI. I am looking to have a different

We have the following classes @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) // optional annotation as this is default @DiscriminatorColumn(name = "apType", discriminatorType = DiscriminatorType.STRING, length = 255) @DiscriminatorValue("AP") public class ApplicationProcess { } And this @Entity @DiscriminatorValue("APS") public class ApplicationProcessScheme extends ApplicationProcess { } Now I need to know at runtime if the ApplicationProcess is of DiscriminatorValue AP or APS . Since this is automatically handled by jpa, I have no way of getting this value. We are calling a

Is there explicit support for Single Table Inheritance in Django? Last I heard, the feature was still under development and debate. Are there libraries/hacks I can use in the meantime to capture the basic behavior? I have a hierarchy that mixes different objects. The canonical example of a corporation structure with an Employee class, subclasses for types of employees, and a manager_id (parent_id) would be a good approximation of the problem I am solving. In my case, I would like to represent the idea that an employee can manage other employees while being managed by a different employee.

I am having a problem getting Devise to work the way I'd like with single table inheritance. I have two different types of account organised as follows: class Account < ActiveRecord::Base devise :database_authenticatable, :registerable end class User < Account end class Company < Account end I have the following routes: devise_for :account, :user, :company Users register at /user/sign_up and companies register at /company/sign_up . All users log in using a single form at /account/sign_in ( Account is the parent class). However, logging in via this form only seems to authenticate them for the

My Rails views and controllers are littered with redirect_to , link_to , and form_for method calls. Sometimes link_to and redirect_to are explicit in the paths they're linking (e.g. link_to 'New Person', new_person_path ), but many times the paths are implicit (e.g. link_to 'Show', person ). I add some single table inheritance (STI) to my model (say Employee < Person ), and all of these methods break for an instance of the subclass (say Employee ); when rails executes link_to @person , it errors with undefined method employee_path' for #<#<Class:0x000001022bcd40>:0x0000010226d038> . Rails is