Why QueryTrackingBehavior should not be NoTracking by default?
<p>While looking for a workaround for Entity Framework 7 RC1 problem (setting entities state as Added after ToList() for complex queries), I found db.ChangeTracker.QueryTrackingBehavior property and set it to NoTracking. This fixed the problem.</p>

<p>I like this approach more because it allows me to manually control what's written to the database - I just need to mark all changed or added entities as Changed/Added.</p>

<p>Is there a drawback with this approach rather then a need to manually set state of modified entities as modified?</p>