Month: October 2007

Inheritance as it pertains to objects is pretty easy to understand and represent. There are lots of complications and benefits that most developers these days understand well. It is also possible to represent inheritance in a relational model, which is effectively a 1:1 relationship between tables. For example you might have the following table schema:

In this schema you would have foreign keys going from Customer and Employee to person. It’s a way to normalize your data that is similar to inheritance. This is something that I have wanted to support in NBusiness but it is a little tricky as you might imagine. What principles of class inheritance apply to Entities as well, I’m not entirely sure? In the case of entities it’s mostly about inheriting data and behaviors and you don’t really have encapsulation or polymorphism.

I’ve been thinking a lot about this after someone at last weekend’s code camp asked me a question about whether or not it was possible to have entities only retrieve subsets of data. The answer to that questions is a tentative ‘yes’ but in fact it would require a fair amount of manual work to get your stored procedures to map back to the correct tables. It’s possible but you’d lose a lot of the benefits of code generation.

So after thinking about this a bit I realized that the two problems (entity inheritance and retrieving subsets of data) had something in common, which I’m calling data hiding for now. In both situations you may only want a subset of data and behaviors from the base entity so I’m thinking of adding a “hide” keyword which will allow you to not inherit fields, properties and rules from the base entity.

In fact I’m thinking about the possibility of creating a new type called use case or something like that. A use case would be just like an entity except that it can only inherit fields, it cannot declare them, sort of like a reverse abstract class. Also a use case must always inherit from an entity. I would imagine that you could create sub families below your root entity definitions and here you would create specific use case definitions. Or maybe model would be a better keyword? Actually I rather like that now that I think about it. The sub families would be more like the use case while the models will describe the various components of a use case.

So suppose you have a Customer entity, if a user logs in and is a Customer you have one use case where they are managing a customer data and have a variety of behaviors associated with that. In this use case they may only have a subset of customer data available to them for editing. Now you may also have a different use case where an administrator of the application logs in and needs to be able to edit a different subset (or complete set) of customer data. As it is now if you declared two different Customer entities for the different use cases you would need to then create the tables and stored procedures to allow them to share the data. With entity inheritance and models you would be able to much more effectively express data hiding while maintaining the ability to share data.

I will work out the details a little bit more but for now check out my wiki page on Entity Inheritance with a little more detail and an example. These features are starting to clarify a bit more in my head; you can look forward to a few other cool features soon such as:

·         Dynamic SQL Fetching (v2.1)

·         CSLA Templates

·         VS 2008 compatibility (v3.0)

·         LINQ support (?)

·         Entity Attributes

·         Partial Entities

·         Custom authorize / access rules

·         Validation rules that apply to only certain CRUD operations

·         Validations warnings and info

Also, one last interesting thing is that I fired off an email To Scott Guthrie at Microsoft the other day asking him about the MVC framework they’re working on. He responded by telling me that they’ll be giving me an advanced preview of the framework in a couple of weeks which is really exciting! It really looks like NBusiness could be a natural fit for the MVC framework and I’m pretty excited to check it out. I’m glad to see that they’re having such an open relationship with open source projects.