Hi all, I just posted a technical question, but I also have a more general design question, that is probably not really specific to DataMapper.
I have a set of classes along the following lines: class Item end class Note < Item class Knife < Item etc. etc. This can become quite a long list. Since they are single table inheritance, all the information ends up in one SQL table. I.e. notes have titles and contents, which means that now every item (incl. e.g. knives) have a "title" and "content" field. Not in the class definition, of course, but in the SQL table. My simple question is: is this bad design? Does this lead to super inefficient database usage? Or is this just fine and common? In terms of practical usage and coding, the inheritance definitely brings substantial benefits. Jos --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
