What about single table inheritance? I might have 10 different Ruby
classes pointing to the same table. By using such strict type
enforcement, you are limiting the demands the system may have in the
future. If you want to know you are writing to the correct table,
check that with model.class.table_name.
On Aug 29, 2006, at 4:28 PM, Joe Auricchio wrote:
Not to put words in Chris's mouth, but it seems to me that he wants
to ensure the objects in question are all of the same ActiveRecord
class, which means they'll be written back to the same table and
represent the same kind of data. That's a legitimate concern for
business logic: ensuring we're actually working with the data we
intend to.
On Aug 29, 2006, at 2:51 PM, Michael Genereux wrote:
Trying but failing? ;-)
You're on the money on what I meant. I look forward to Chris'
impressions of our answers.
On 8/29/06, Jordan A. Fowler <[EMAIL PROTECTED]> wrote:
What Michael is trying to say: Instead of just checking the type of
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
