I have three unique entity classes that each have a collection of a
fourth entity via the HasMany attribute. The mappings should be one-to-
many unidirectional relationships from entities A, B, and C to entity
D. Each HasMany attribute references the same table and the same
column for the foreign key. Since the referenced column is an integer
it should not matter that it could be pointing to objects from 3
tables. The problem is that the generation tool non-deterministically
picks one of the first three entities and creates a foreign key
relationship from the reference column in the 4th entity table to the
entity that owns that relation. Is there any way for me to override
this behavior and make it so that the Many side of the HasMany
relationship doesn't foreign key back to the first table?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to castle-project-users@googlegroups.com
To unsubscribe from this group, send email to
castle-project-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---
