blocks|key|1072591|text|这将很快成为一个名为EntityFramework.Migrations的NuGet包|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1072592|Scott+Hanselman在TechEd+2011上进行了演示(可在http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DEV349在线获得)。相关部分为45分钟。|offset|length|1072593|简而言之，安装软件包后，您将在package+Manager控制台中输入以下内容，以生成数据库更改脚本：|1072594|migrate+-script|code-block|syntax|javascript|1072595|更新(2011年11月13日)|style|BOLD|1072596|这个包的Alpha3版本现在可以在NuGet上使用。它不使用上面提到的cmdlet+migrate+-script，而是使用cmdlet+Add-Migration+<migrationname>。可以在ADO.NET团队博客上找到walk-through+of+its+use。|CODE|1072597|更新(2012年2月14日)|1072598|从4.3版开始，此功能已作为主EntityFramework+NuGet+package的一部分提供。可以在ADO.NET团队博客上找到使用EF+4.3的updated+walk-through。|1072599|entityMap|0|LINK|mutability|MUTABLE|url|http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DEV349|1|http://blogs.msdn.com/b/adonet/archive/2011/09/21/code-first-migrations-alpha-3-no-magic-walkthrough.aspx|2|http://nuget.org/packages/EntityFramework|3^0|0|10|1R|0|0|0|0|0|F|0|16|F|1X|T|38|N|1|0|0|E|0|F|T|2|25|K|3|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|F|3|G|5|6|7|1F|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1H|8|@$D|1I|E|1J|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@$D|1L|E|1M|O|S]|$D|1N|E|1O|O|S]]|9|@$D|1P|E|1Q|1|1R]]|A|$]]|$1|T|3|U|5|6|7|1S|8|@$D|1T|E|1U|O|P]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1V|8|@]|9|@$D|1W|E|1X|1|1Y]|$D|1Z|E|20|1|21]]|A|$]]|$1|X|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]|15|$5|10|11|12|A|$13|16]]|17|$5|10|11|12|A|$13|18]]|19|$5|10|11|12|A|$13|18]]]]

This will be coming soon as a NuGet package called EntityFramework.Migrations

A demo was performed by Scott Hanselman at TechEd 2011 (available online at <a href="http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DEV349" rel="noreferrer">http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DEV349</a>). The relevant section is 45 minutes in.

In short, once the package is installed, you'll enter the following into the Package Manager Console to generate a database change script:

<pre><code>migrate -script
</code></pre>

UPDATE (13-Nov-2011)

The alpha 3 build of this package is now available on NuGet. Rather than use the cmdlet <code>migrate -script</code> mentioned above, it uses the cmdlet <code>Add-Migration &lt;migrationname&gt;</code>. A <a href="http://blogs.msdn.com/b/adonet/archive/2011/09/21/code-first-migrations-alpha-3-no-magic-walkthrough.aspx" rel="noreferrer">walk-through of its use</a> can be found on the ADO.NET team blog.

UPDATE (14-Feb-2012)

This functionality is now available as part of the main <a href="http://nuget.org/packages/EntityFramework" rel="noreferrer">EntityFramework NuGet package</a>, starting with version 4.3. An <a href="http://nuget.org/packages/EntityFramework" rel="noreferrer">updated walk-through</a> using EF 4.3 can be found on the ADO.NET team blog.

blocks|key|1072522|text|您可以尝试Wizardby：这是一个用于管理数据库迁移的工具。它没有与EF集成(因为在这方面几乎不可能与它集成)，但它可以完成这项工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1072523|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/octalforty-wizardby/^0|5|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can try <a href="http://code.google.com/p/octalforty-wizardby/" rel="nofollow noreferrer">Wizardby</a>: this is a tool for managing database migrations. It doesn't integrate with EF (since it's nearly impossible to integrate with it in this respect), but does the job.

blocks|key|1072560|text|ScottGu在blog+entry中提到了一些关于这方面的内容|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1072561|1072562|我们还将在未来支持EF的“迁移”功能，这将允许您以编程方式自动化/编写数据库模式迁移。|blockquote|1072563|1072564|1072565|编辑|1072566|我认为他可能指的是Morteza+Manavi在another+SO+answer中回答的Entity+Designer+Database+Generation+Power+Pack。|1072567|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2011/01/11/vs-2010-sp1-and-sql-ce.aspx|1|https://stackoverflow.com/questions/4221938/how-to-do-migration-when-generate-database-from-model-in-entity-framework-model-f|2|http://visualstudiogallery.msdn.microsoft.com/df3541c3-d833-4b65-b942-989e7ec74c87/^0|8|A|0|0|0|0|0|0|0|O|H|1|19|1A|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|-4|5|6|7|13|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|14|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|16|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]|$A|1C|B|1D|1|1E]]|C|$]]|$1|N|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]|X|$5|Q|R|S|C|$T|Y]]]]

ScottGu mentions something about this in a <a href="http://weblogs.asp.net/scottgu/archive/2011/01/11/vs-2010-sp1-and-sql-ce.aspx" rel="nofollow noreferrer">blog entry</a>:

<blockquote>
 We are also going to be supporting a “migrations” feature with EF in the future that will allow you to automate/script database schema migrations programmatically.
</blockquote>

[EDIT]

I think he might be referring to the <a href="http://visualstudiogallery.msdn.microsoft.com/df3541c3-d833-4b65-b942-989e7ec74c87/" rel="nofollow noreferrer">Entity Designer Database Generation Power Pack</a>, as answered by Morteza Manavi in <a href="https://stackoverflow.com/questions/4221938/how-to-do-migration-when-generate-database-from-model-in-entity-framework-model-f">another SO answer</a>.

blocks|key|1072481|text|好吧，如果你想像ActiveRecord一样工作，那么你需要像ActiveRecord一样工作。:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1072482|但是，如果您想使用模型优先，但仍然使用迁移，这是可能的，但需要为您做额外的工作。Model-first将生成一个数据库更改脚本。您必须将相关部分提取到迁移中，以及手动编写撤消脚本。虽然这涉及到一些体力劳动，但我并不觉得它非常困难。|1072483|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well, if you want to work like ActiveRecord, then you need to work like ActiveRecord. :) 

However, if you want to use model-first but still use migrations, this will be possible, but will require extra work on your behalf. Model-first will generate a database change script. You will have to extract the relevant parts into migrations, as well as manually writing undo scripts. Although this involves some manual labor, it doesn't strike me as terribly difficult.

blocks|key|2482804|text|我正在开发一个EF.Migrations库的替代品--+EntityFramework.SchemaCompare。它允许将db模式与表示数据库上下文的实体模型进行物理比较(EF.Migrations不能做到这一点)。这可以在数据库初始化期间触发，也可以在请求时手动触发。考虑下面的例子|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2482805|#if+DEBUG
Database.SetInitializer(new+CheckCompatibilityWithModel<DatabaseContext>());
#endif|code-block|syntax|javascript|2482806|如果发现不兼容问题，它将在数据库初始化期间抛出异常，描述数据库模式和模型之间的差异。或者，您可以通过以下方式随时在代码中找到这些差异|2482807|using+(var+ctx+=+new+DatabaseContext())
{
++++var+issues+=+ctx.Database.FindCompatibilityIssues();
}|2482808|然后，有了这些差异/不兼容问题，您可以更新db模式或模型。|2482809|当您需要完全控制数据库模式和模型设计和/或在一个团队中工作时，这种方法特别有用，其中多个团队成员在同一个数据库模式和模型上工作。除了EF.Migrations之外，它还可以使用。|2482810|在GitHub上为我分叉：https://github.com/kriasoft/data|2482811|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/kriasoft/data|1^0|S|T|0|0|0|0|0|0|0|D|W|1|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|16|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|17|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|19|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|S|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|Z]]]]

I'm working on an alternative to EF.Migrations library - <a href="https://github.com/kriasoft/data" rel="nofollow">EntityFramework.SchemaCompare</a>. It allows to physically compare a db schema with an entities model representing database context (EF.Migrations doesn't do it). This can be fired either during database initialization or manually on request. Consider the following example

<pre><code>#if DEBUG
Database.SetInitializer(new CheckCompatibilityWithModel&lt;DatabaseContext&gt;());
#endif
</code></pre>

It will throw an exception during database initialization describing the differences between db schema and model if incompatibility issues are found. Alternatively you can find those differences at any time in your code this way

<pre><code>using (var ctx = new DatabaseContext())
{
 var issues = ctx.Database.FindCompatibilityIssues();
}
</code></pre>

Then having those differences / incompatibility issues on hands you can either update the db schema or the model.

This approach is particularly useful when you need complete control over the database schema and model design and/or working in a team where multiple team members are working on the same db schema and model. It can also be used in addition to EF.Migrations.

Fork me at GitHub: <a href="https://github.com/kriasoft/data" rel="nofollow">https://github.com/kriasoft/data</a>

I've been playing with Entity Framework 4, using the model driven approach to generate the database script from my entities. This is great but I'm not sure how this works when it comes to versioning the database. I'm guessing if I wanted to use an active record type migration framework I'd have to work the other way around and generate my entities from my database? Is there any way to use the model driven approach and version the database properly?

Database migrations for Entity Framework 4

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我一直在使用Entity Framework4，使用模型驱动的方法从我的实体生成数据库脚本。这很棒，但是当涉及到数据库版本控制时，我不确定它是如何工作的。我猜，如果我想使用活动记录类型的迁移框架，我必须以另一种方式工作，并从我的数据库生成我的实体？有没有办法使用模型驱动的方法并正确地对数据库进行版本控制？

问Entity Framework 4的数据库迁移
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Entity Framework 4的数据库迁移EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Entity Framework 4的数据库迁移
EN