The SQL Server View comes with cache effects ?!

Condition:

1. Entity Framework Code First

2. The same context (or a transaction)

3. Use MSSQL

 

First, query a view, update the table associated with the composition view, and then query the view with the same conditions. No updated data is obtained.

If you place the same query conditions in another context, you can obtain the updated data.

If the conditions change, for example, from Name = 'A' programming Name = 'B', you can obtain the updated data.

 

Probably as follows:

Using (Context c)

{

C. View. Where (e => e. Name. Equals (""));

C. Table. Update (); // View is composed of a Table and another Table.

C. view. where (e => e. name. equals ("A"); // The data is actually updated, but not the updated data. If you change A to B, you can get the data.

// In addition, I have observed SQL statements through SQL Profile. Everything is normal. Three SQL statements are executed in the database.

}

 

At present, I have not studied this problem in depth. I don't know whether it is a database problem, An ADO problem, or an EF problem.

 

Annoying !!!!!