Hi Dan,
it's true the exception is a bit misleading in the case of as enum mapping,
you also need to specify the element and the column mappings.
so it becomes something like:
[HasMany(Table = "Roles", ColumnKey = "UserId", Element = "RoleId",
ElementType = "Namespace.Model.Role, Assembly")]
public virtual IList<Role> Roles
{
...
}
I've committed some code to the trunk that can guess these properties if you
leave them blank, so if you upgrade
[HasMany(Table = "Roles")]
public virtual IList<Role> Roles
{
...
}
should work as expected and generated the same mapping as the version above.
cheers
Ernst.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Users" 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/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---
