Jan 13, 2015 at 6:22 PM
Edited Jan 27, 2015 at 8:53 AM
In our project we use Effort
framework with NMemory database under the hood. The database is created automatically from the Code First classes. Due to some circular references in the data model (for
historical reasons) we have troubles inserting cross-referencing records (A references B whilst B references A, and the link is non-optional).
NMemory appears to provide
for disabling foreign key constraints.
.GetAllRelations() method always returns an empty list, and I see in the debugger that both collections
are always empty. I don't exclude that Effort is somehow misusing NMemory, but this is just an observation which right now isn't a real problem.
The relations I need are actually stored only in
collection, to which unfortunately I have no public access. Internal methods
do exist and aren't used from within the NMemory assembly, which makes me believe then were originally planned as public methods.
I would be happy if
TableCollection.relationMapping collections were synchronized by some internal mechanism
- Or the library gave some public access to
TableCollection.relationMapping, e.g. by declaring methods
GetReferredRelations as public.
Anyway it looks like
field was added (in rev
) in a rather unclean way...
Could you please have a look?