Hello,
I have a situation something like this:
// Yes, A is abstract
abstract class A {}
// B is not abstract, could inquire about B's
class B : A {}
// C is also not abstract, most of the app wants to work with C's
class C : B {}
In practice, something like this:
abstract class Credential {}
class User : Credential {}
class SimulatorUser : User {}
But we'll focus on the ABC's for now.
My table design is table per class.
CREATE TABLE A (...);
CREATE TABLE B (...);
CREATE TABLE C (...);
And my mappings are:
class AMap : ClassMap<A> {}
class BMap : SubclassMap<B> {}
class CMap : SubclassMap<C> {}
I exported the configuration, and it seems that A (Credential) was
mapped correctly.
However, it seems that B (User) failed to map; neither did C (SimulatorUser).
The obvious first question is, multiple-subclass, table-per-class is
supported along these lines?
I don't mind inheriting from BMap,if that's what it takes, but might
like to preserve the B mapping at the same time, if possible.
Any suggestions?
Regards,
Michael Powell
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to fluent-nhibernate+unsubscr...@googlegroups.com.
To post to this group, send email to fluent-nhibernate@googlegroups.com.
Visit this group at https://groups.google.com/group/fluent-nhibernate.
For more options, visit https://groups.google.com/d/optout.
