Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It looks like you didn't have specified the <code>stamp</code> property as a rowversion in your model and it is just a binary field. You can specify it with Fluent API:</p> <pre><code>modelBuilder.Entity&lt;Driver&gt;().Property(d =&gt; d.stamp) .IsRowVersion() .IsConcurrencyToken(false); </code></pre> <p>The code above is for the case when you don't want to have the <code>stamp</code> property as a concurrency token. (A rowversion is a concurrency token by default, so you have to disable it explicitly.) If you want to have it as concurrency token, then you can use with Fluent API...</p> <pre><code>modelBuilder.Entity&lt;Driver&gt;().Property(d =&gt; d.stamp) .IsRowVersion(); </code></pre> <p>...or with data annotations:</p> <pre><code>[Timestamp] public byte[] stamp { get; set; } </code></pre> <p>This should prevent EF to write an UPDATE for this property.</p> <p><strong>Edit</strong></p> <p>If you use Database-First strategy the <code>[Timestamp]</code> attribute does not work. This attribute is only for Code-First development.</p> <p>When you use Database-First the connection string contains a metadata section refering to the EDM defined in the EDMX file:</p> <pre><code>connectionString="metadata=res://*/Model1.csdl |res://*/Model1.ssdl |res://*/Model1.msl; ... ..." </code></pre> <p>If Entity Framework finds this section in the connection string it doesn't use data annotations on model properties nor does it process any code in Fluent API (<code>OnModelCreating</code> isn't called at all). Instead it loads the mapping definitions from the embedded and compiled EDMX file.</p> <p>That means, if you want to define the <code>stamp</code> property as a concurrency token you <em>must</em> do this in the EDMX file. In XML it would look like this:</p> <p>In SSDL section:</p> <pre class="lang-xml prettyprint-override"><code>&lt;Property Name="stamp" Type="timestamp" Nullable="false" StoreGeneratedPattern="Computed" /&gt; </code></pre> <p>In CSDL section:</p> <pre class="lang-xml prettyprint-override"><code>&lt;Property Name="stamp" Type="Binary" Nullable="false" MaxLength="8" FixedLength="true" annotation:StoreGeneratedPattern="Computed" ConcurrencyMode="Fixed" /&gt; </code></pre> <p>You can also define this in the model designer in Visual Studio: Mark the <code>stamp</code> property in the entity in the designer surface, go to the Properties Window and set "Concurrency Mode" to "Fixed" (and also set the "StoreGeneratedPattern" to "Computed").</p> <p>You can also remove the metadata section from the connection string. But this effectively means that you switch from database first to code first development. Then all attributes and Fluent API will be respected, but not any definitions in EDMX anymore.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to handle EF 4.3.1 setting Modified a Rowversion Row
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSlauma
    1. USSlauma
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to handle EF 4.3.1 setting Modified a Rowversion Row
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMarking the property as [Timestamp] isn`t solving anything. The problem relies within the `DBContext.Entry(entity).State = EntityState.Modified;`. It marks the stamp property as Modified and during `DBContext.SaveChanges()` it build`s the *dynamic-sql* which updates the column [stamp] in the DB. This is a guess cause of SQLCE I have no profiler to back it up.
      singulars
      1. PO
      1. USCiobanu Ion
    2. CO@CiobanuIon: For SQL Server this is not true. EF doesn't send a SQL which updates a column of a property marked with `[Timestamp]`, instead its value is included in the WHERE clause for optimistic concurrency checking. Did you test that it doesn't work? Which version of SQLCE are you using?
      singulars
      1. PO
      1. USSlauma
    3. COI`m using SQLCE4.0.0.0. Now that I tested if concurrency is working, it`s not. With usual non-detached entities, the update is happening, the [stamp] value is incrementing but the concurrency is not happening. This is unexpected. I`m having a database first case. Generated POCOclases from EF4.x DbContext Generator and decorated them with DataAnnotations. Really unsure where to look now. On the previous matter, my guess was if I can`t set Modified to the whole entity I set only some properties as Modified, and update worked. But hard-coding for every property is not a proper solution.
      singulars
      1. PO
      1. USCiobanu Ion
 

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