Cart
[Home] [By Thread] [By Date] [Recent Entries]
Sorry, John, I think your correction was valid, but I wound up arguing against classes being domains, whereas you were really pointing out that tables were not domains. Tables do not represent domains, gotcha. Except... To a relational mind, classes may represent a type or an entity. You're suppose to model entities to tables and types to columns. The problem is that the interpretation of what constitutes and entity vs. type is subjective. It depends on how the data will be used, and different viewpoints may coexist for the same implementation. So there's some remarkable subtleties in the argument for mapping a class to a domain. Personally, I'm struggling with trying to grasp why a proposition isn't just another kind of type. It seems to my poor eyes that the only real difference between proposition and domain is are the functional aspects of the two (with propositions having special processing capabilities). In other words, propositions are native types of the relational model. I hope this essay answer scores a better grade.
|
