You can map it as readonly, I guess.
On Mon, Feb 9, 2009 at 9:13 PM, Graham Bunce <[email protected]>wrote:
>
> Hi,
>
> I have an abstract base class that implements a protected property
>
> protected string Identifier { get { return _value; } }
>
> The classes that inherit from this base class provide "business
> context" to the data. So they might have
>
> public int ReworkId { get { return int.Parse(base.Identifier); } }
>
> Now the mapping file contains a reference to Identifier in the base
> class but not to the "ReworkId" in the extends mapping file. When I do
> a query (e.g. Linq2NHib) on the extended class using the ReworkId it
> fails. This is obvious, as the ReworkId is not in the mapping.
>
> My problem is that I don't want it in the mapping as it really isn't
> needed - it's only a rename of the base class protected property.
>
> Is there any way to identify a value to the mapping file of the
> inheriting class without actually mapping back to the database - i.e.
> to force the generated SQL to know it should be using the base class
> Identifier? If not, is there another way I can do (or design) this?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
