We use do.net in our project here and are having some performance issues. To solve some of these issues we are going to use Indexed Views.
I found the MaterializedViewAttribute, does that do anything?
If I create the views, can I mark a class read-only so no one accidentally tries to update from the class?
I can also use getter only properties but read-only would be much clearer.
All you really need is an attribute that says "don't try to do anything with this object. When it goes to run, trust me it will work". That way you give a lot of flexibility in the model without trying to solve all of the problems. This is the second time I have tried to use DO.net and both times I have run into problems with enterprise level functionality. Sometimes you have to give customers enough flexibility to hang themselves with.
I would love to be able to use this product over a data warehouse for reporting. Unfortunately, this feature is going to push me to use Entity framework for this solution because I can just turn off all validation and it goes into the "trust the developer" mode. Even better, EF will allow me to do this at the context level, so I don't have to allow it to do any validation.
In many cases the handling of schema etc... is done by a dba team and we developers have no control. With the approach do.net took, you have essentially limited your product to smaller silo applications
answered Apr 26 '12 at 14:58
It is supposed to be used on persistent interfaces to turn them into materialized views either native or emulated via tables.
You can create views, but those would not be utilized by DO.Net.
answered Apr 25 '12 at 04:34