Frederick, because the "purchase_type" column would still be in the "payments" table, like in usual polymorphic association.
I am in fact questioning myself if there are any benefits over the usual polymorphic association. I thought at first that it would be nice to be able to delete purchases tables if necessary (to clear for example member's purchase history) and not to have to have anything to do with the payments table (with usual polymorphic association i would need to at least nullify the foreign keys), and also i would only need to impose uniqueness constraints on foreign keys, and not on the pair [type, foreign key]. But on the other hand, i would not be able to ensure that there are no references from two different "purchases" tables to the same record in "payments" table... So i am hesitating. Alexey. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
