To paraphrase my question, so that it will have more context:
I have a need to store different collections of pricing information or
hourly rates.
For a given entity (say, an Employee), I will have: HourRates,
ExternalHourRates, EventHourRates and so on.
Each type of "rate" is holds these three values:
Valid from, Valid to, Amount.
I tried to model my entity like so:
class AmountInfo
{
class Employee
{
public virtual ISet<AmountInfo> HourRates { get; set; }
public virtual ISet<AmountInfo> ExternalHourlRates { get; set; }
}
but NHibernate would create just one table and put them all inside
that table. So HourRates and ExternalHourRates were efectively the
same.
Then, I introduced subclasses
On Aug 9, 5:46 pm, Miha V <[email protected]> wrote:
> Hi!
>
> I have a one-to-many association between several entities. That's also
> the reason I'm not using bidirectional mapping.
[...]
--
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.
