I am running exactly into same issue.
Is there already a bug for this?
Thanks, Stefan
--
You received this message because you are subscribed to the Google Groups
nhusers group.
To post to this group, send email to nhus...@googlegroups.com.
To unsubscribe from this group, send email to
why not joined-subclass ?
On Thu, Dec 2, 2010 at 7:20 PM, Hendry Luk hendrym...@gmail.com wrote:
Yes, in this case, because Employee has association to Company, and also
other properties. Is there any other way to achieve that other than
subclassjoin?
On Thu, Dec 2, 2010 at 11:32 PM, Fabio
Because joined-subclass can't be mixed with discriminator subclass within
the same inheritance hierarchy. Like I mentioned in my post, I need to use
discriminator-subclass because other subclasses do not have additional
properties (only different behavior implementations).
On Sat, Dec 4, 2010 at
Hello,
Is there any way to make one-many bag association from an entity to a
subclass (with join)?
Just an isolated example:
class name=Person
!-- blah blah --
discriminator column=PersonType /
/class
subclass name=Employee discriminator-value=Employee
!-- blah blah --
join table=Emplooyee
key
are you using subclass+join for some special reasons ?
On Thu, Dec 2, 2010 at 6:45 AM, Hendry Luk hendrym...@gmail.com wrote:
Hello,
Is there any way to make one-many bag association from an entity to a
subclass (with join)?
Just an isolated example:
class name=Person
!-- blah blah --
Yes, in this case, because Employee has association to Company, and also
other properties. Is there any other way to achieve that other than
subclassjoin?
On Thu, Dec 2, 2010 at 11:32 PM, Fabio Maulo fabioma...@gmail.com wrote:
are you using subclass+join for some special reasons ?
On Thu,
I've got a Recipe class, that contains lists of three different types
of Ingredient Uses. These classes all inherit from the base,
IngredientUse. So the mapping for the IngredientUse looks like this:
class name=IngredientUse table=IngredientUses
id name=Id type=Int64 column=Id
