Or in your get property,
get{
dateval.Date
}
On 10/27/09, Diego Mijelshon <[email protected]> wrote:
> Hi everyone,
>
> I'm trying to find an adequate mapping for a legacy data model that I have.
>
> Data Model:
> [image:
> ?ui=2&view=att&th=12497a77871aee8e&attid=0.1&disp=attd&realattid=ii_12497a77871aee8e&zw]
>
> All Primary Keys are identity fields.
>
> Class model:
> [image:
> ?ui=2&view=att&th=12497ae6c05e8d8c&attid=0.1&disp=attd&realattid=ii_12497ae6c05e8d8c&zw]
>
>
> The document's type code could be used as a discriminator for the detail
> type, although there are more values than detail types (let's say you have
> X1, X2, Y and Z4).
>
> Of course, my question is: what's the correct mapping for this models?
> According to the docs, I can't use identity keys with the table-per-concrete
> class approach, which is the one that more accurately matches what I have.
> "Table per concrete class, using implicit polymorphism" looks like a
> suitable approach, although I'd like to avoid having 3 queries for each
> document.
>
> Thanks in advance!
>
> Diego
>
> >
>
--
Sent from my mobile device
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
