Timeline for This LINQ Model Query seems extremely inefficient
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 13, 2012 at 13:34 | comment | added | Jeff Mercado | @Groo: You know, I didn't even notice the names of those properties on the entities. I definitely agree with that. Though it'd be moot if they can't be renamed in the DB. Even though the names of the entities and their properties doesn't necessarily have to match that of in the DB, they should always match IMHO. | |
| Jul 13, 2012 at 7:51 | comment | added | vgru |
+1 But I would also ditch the "Collection" prefix out of every property which belongs to a Collection class. Collection.Name and Collection.Type should be enough. On the other hand, the class itself should probably be renamed to FigureCollection (if that's what it's used for) or something similar which would explain what data it contains.
|
|
| Jul 13, 2012 at 1:31 | comment | added | mawburn | Great! Thanks. I was wondering how I could better use those associations! | |
| Jul 13, 2012 at 1:28 | vote | accept | mawburn | ||
| Jul 13, 2012 at 0:56 | history | answered | Jeff Mercado | CC BY-SA 3.0 |