Sibling Relationship Naming conflict


Calling one entity Product and another one ProductColor and assigning a sibling relationship between them will cause a compile error with the message ""An item with the same key has already been added." This is undoubtedly due to a dictionary using the names of the entities and relationships incorrectly to create the same dictionary key twice and blowing up. Find out where it is happening and make the dictionary keys more unique.
Closed Dec 8, 2007 at 5:13 PM by justinc


justinc wrote Oct 30, 2007 at 12:54 AM

Additionally stored procedures will be named something similar to "ProductsFetchAll" or "{name}FetchAll" which ends up causing problems if two relationships on different entities are named the same thing. It should be named something more like:


wrote Nov 17, 2007 at 9:08 PM

wrote Dec 8, 2007 at 6:46 AM

wrote Dec 8, 2007 at 5:13 PM

Resolved with changeset 29067.

wrote Feb 13, 2013 at 2:14 AM

wrote May 16, 2013 at 1:36 AM