Even though I can modify the schema in this case, it's really a
virtual model that I'm after.
I want to have something that I can use inside NH with it's caching
and querying capabilities, compose easily from the existing data, and
something that is immutable.
Perhaps I should have created a VIEW in the schema and tried to map to
that, it would be essentially the same.
But, is that a recommended approach for these scenarios?
On May 21, 10:20 am, Hudson Akridge <hudson.akri...@gmail.com
> That works :)
> You may also look at mapping those two parts polymorphicly, i.e. map an
> IPart to an I_Parts table, then map a Part as a join subclass to IPart, with
> it's table of Parts, then map the ReadOnlyPart to a join subclass with IPart
> with it's table of ProductionParts.
> That would of course mean that the I_Parts table contains an index of both,
> but the actual fields that represent the part would exist in two separate
> tables which could then have various read-only and read-write attributes
> placed upon them.