Quantcast
Channel: Entity Framework
Viewing all articles
Browse latest Browse all 10318

Edited Issue: Migrations table insert query too long when fully-qualified type name has nesting. (ContextKey column) [535]

$
0
0
When first running Build.cmd, two tests fail. Upon subsequent runs, these tests pass, because the database has already been initialized. These are the two tests:<br />E:\git\entityframework\test\EntityFramework\FunctionalTests\ProductivityApi\DbContextTests.cs<br />Database_name_generated_from_generic_DbContext_class_name_works()<br />Database_name_generated_from_generic_DbContext_class_nested_in_generic_class_name_works()<br /><br />The issue is in the SQL query that gets generated to add the InitialCreate migration -- it is too long and SQL throws an error saying it would be truncated. I've attached the statement generated by one of the tests.<br /><br />In the unit tests, the type nesting looks like this:<br />GT<NT, NT>.GenericFuncy<GT<GT<NT, NT>, NT>, NT>()<br /><br />Solution might be to compress or truncate the value for that column.

Viewing all articles
Browse latest Browse all 10318

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>