Two entities for one table

I wonder if it makes sense to have more than one entity for a table. One Entity with onyl a subset of fields (eg just for lookup matters or validation) and another Entity for CRUD operations.

Or is this a bad idea and produces just Overhead?

Thanks for an answer!

That's possible and can be useful in some situations. You can even use multi-model design to put different classes in different models, if you need to: http://www.tmssoftware.biz/business/aurelius/doc/web/multi-model_design.html