Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In response to "What is the EdmMetadata hash being compared against?"</p> <p>The EdmMetadata table allows Code First to determine if the model in your code is the same as the model in your database. The table contains a single row which is a hash of your SSDL. SSDL stands for Store Schema Definition Language and is an XML based language used to describe an Entity model and the mappings between models.</p> <p>You can read more about SSDL and view the specification at <a href="http://msdn.microsoft.com/en-us/library/bb399559.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/bb399559.aspx</a> </p> <p>You mention that things work fine locally but not in production. Are you allowing Code First to build both the local and production databases? Is the production database already existing or being generated in another fashion?</p> <p>CodeFirst is reporting that the hash in the database doesn't match the present model's hash so something must be different. Figuring out what may be a challenge.</p> <p>The EdmMetadata table is mapped to the EdmMetadata class. There is a TrygetModelHash method in this class which you can use to get the hash for a given context. If you're desparate you could use this to compare your current model to the hash that's in your production database. This would at least keep you from having to build a new database constantly just for testing.</p> <p>You can also instruct Code First to exclude the EdmMetadata table if desired.</p> <pre><code>protected override void OnModelCreating(DbModelBuilder modelBuilder) { modelBuilder.Conventions.Remove&lt;IncludeMetadataConvention&gt;(); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POEF Code First thinks database is out of date -- only in production
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMark
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEF Code First thinks database is out of date -- only in production
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Mark, There is *no* difference between my test db and my production db. Exact same .sdf file. I'm just copying the file to the production server. Here's my basic workflow: 1. Edit a POCO entity. 2. Test/Debug my app (locally). 3. Receive "The model backing 'foobar' context has changed...". 4. Think "Oh yeah, I have to regenerate the database!" 5. Run custom db generator that recreates db and seeds w/ data. 6. Test/debug app again (locally) --> works fine. 6. Publish app to production server (ftp). 7. Open a page in browser. 8. Receive "The model backing 'foobar' context has changed...". Why?
      singulars
      1. PO
      1. USdevuxer
    2. CO@Mark, Please see my latest edits.
      singulars
      1. PO
      1. USdevuxer
    3. COCan you give TryGetModelhash a try? Compare the value it returns against the ModelHash in the production and local EdmMetadata table. The values must be different or you wouldn't receive that error. Why they're different we'll have to figure out. I'd first start with that though. Verify the hashes actually are different and you're not running into a bug of some type.
      singulars
      1. PO
      1. USMark
 

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