Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is no IDbContext because it would be useless, the only implementation of it would be the DbContext.</p> <p>EF team is also going this way with IDbSet if you look at this <a href="https://entityframework.codeplex.com/wikipage?title=Design%20Meeting%20Notes%20-%20May%2016,%202013" rel="nofollow">design meeting note</a></p> <p>For me, the real problem with EF when it comes to unit testing is the DbConnection in the DbContext, fortunately there is <a href="https://effort.codeplex.com/" rel="nofollow">Effort</a> a nice project on codeplex that starts to fill this.</p> <blockquote> <p>Effort is a powerful tool that enables a convenient way to create automated tests for Entity Framework based applications. It is basically an ADO.NET provider that executes all the data operations on a lightweight in-process main memory database instead of a traditional external database. It provides some intuitive helper methods too that make really easy to use this provider with existing ObjectContext or DbContext classes. A simple addition to existing code might be enough to create data driven tests that can run without the presence of the external database.</p> </blockquote> <p>With this, you can leave your DbContext and DbSet as is and do your unit tests easily. The only drawback with this is the difference between Linq providers where some unit tests may pass with effort and not with the real backend.</p> <p><strong>UPDATE with EF7</strong></p> <p>I still maintain that IDbContext would be useless and the problem comes from the DbConnection.</p> <p>EF7 will not have an IDbContext either, in order to do unit testing they are now giving an in memory provider.</p> <p>You can see Rowan Miller doing a demo here: <a href="http://channel9.msdn.com/events/Ignite/2015/BRK3727" rel="nofollow">Modern Data Applications with Entity Framework 7</a></p>
    singulars
    1. This table or related slice is empty.
    1. POWhy DbContext doesn't implement IDbContext interface?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSwell
    1. USSwell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COThis would not be useless at all. Right now we are using WCF Data Services that relies on DBContext instance. If it relied on the interface we would be able to get access to the Set<T>() method call and provide the filtering layer which we desperately need (and query interceptors are simply not enough).
      singulars
      1. PO
      1. USpkolodziej
    2. COWith EF6 DbSet's methods are now virtual, you could inherit from DbSet and override needed methods.
      singulars
      1. PO
      1. USSwell
    3. COMS Data Services work directly on DbContext or something that inherits from it. Is there a way to make the Set<> method (which is not virtual even is EF6) return my own DbSet? What I really need to do is filter out the entities (return only some of them).
      singulars
      1. PO
      1. USpkolodziej
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload