Timeline for Tracking Entity Changes (not EF)
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2016 at 14:30 | comment | added | Mathieu Guindon |
Sounds a lot like IList<T>. The problem is that it's the client code that defines the entities, and having to expose IList<T> navigation properties would come as a surprise, since Entity Frameworks' navigation properties must be ICollection<T>.
|
|
| Mar 1, 2016 at 14:28 | comment | added | Pimgd |
@Mat'sMug not really, I tend to program in Java, where Collection<T> comes with addAll(Collection<? extends E> c).
|
|
| Mar 1, 2016 at 14:21 | comment | added | Mathieu Guindon |
Actually, I could... because I'm the one making the ICollection<T> a List<T>... but I don't like using methods of the concrete type when the member is an ICollection<T>... see what I mean?
|
|
| Mar 1, 2016 at 13:44 | comment | added | Pimgd | @Mat'sMug that's a shame. | |
| Mar 1, 2016 at 12:26 | comment | added | Mathieu Guindon |
Nice answer! I can't assume the actual type will have an AddRange member.
|
|
| Mar 1, 2016 at 9:07 | history | answered | Pimgd | CC BY-SA 3.0 |