2017-04-18 07:52:04 +08:00
|
|
|
## EF no longer throws for QueryViews with specific characteristics
|
2017-04-06 04:52:19 +08:00
|
|
|
|
|
|
|
### Scope
|
|
|
|
Edge
|
|
|
|
|
|
|
|
### Version Introduced
|
|
|
|
4.5.2
|
|
|
|
|
|
|
|
### Source Analyzer Status
|
|
|
|
Not planned
|
|
|
|
|
|
|
|
### Change Description
|
2017-04-21 02:19:05 +08:00
|
|
|
|
|
|
|
Entity Framework no longer throws a
|
|
|
|
<xref:System.StackOverflowException?displayProperty=name> exception when an app
|
|
|
|
executes a query that involves a QueryView with a 0..1 navigation property that
|
|
|
|
attempts to include the related entities as part of the query. For example, by
|
|
|
|
calling `.Include(e => e.RelatedNavProp)`.
|
2017-04-06 04:52:19 +08:00
|
|
|
|
|
|
|
- [ ] Quirked
|
|
|
|
- [ ] Build-time break
|
|
|
|
|
|
|
|
### Recommended Action
|
2017-04-21 02:19:05 +08:00
|
|
|
|
|
|
|
This change only affects code that uses QueryViews with 1-0..1 relationships
|
|
|
|
when running queries that call .Include. It improves reliability and should be
|
|
|
|
transparent to almost all apps. However, if it causes unexpected behavior, you
|
|
|
|
can disable it by adding the following entry to the `<appSettings>` section of
|
|
|
|
the app's configuration file:
|
2017-04-06 04:52:19 +08:00
|
|
|
|
|
|
|
```xml
|
2017-04-21 02:19:05 +08:00
|
|
|
<add key="EntityFramework_SimplifyUserSpecifiedViews" value="false" />
|
2017-04-06 04:52:19 +08:00
|
|
|
```
|
|
|
|
|
|
|
|
### Affected APIs
|
|
|
|
* Not detectable via API analysis
|
|
|
|
|
|
|
|
### Category
|
|
|
|
Entity Framework
|
|
|
|
|
2017-04-18 07:52:04 +08:00
|
|
|
<!-- breaking change id: 69 -->
|