Quantcast
Channel: entityframework Issue Tracker Rss Feed
Viewing all 9566 articles
Browse latest View live
↧

Edited Unassigned: Allow generating migration code for a custom MigrationOperation from CSharpMigrationCodeGenerator [2799]

August 20, 2015, 9:30 am
$
0
0
Currently, the CSharpMigrationCodeGenerator must have a specific Generate method for each specific MigrationOperation in the migration. If there is a custom MigrationOperation in the list of migrations, it falls back to the Generate method for the AddColumnOperation, which fails with the following exception:

_The best overloaded method match for 'System.Data.Entity.Migrations.Design.CSharpMigrationCodeGenerator.Generate(System.Data.Entity.Migrations.Model.AddColumnOperation, System.Data.Entity.Migrations.Utilities.IndentedTextWriter)' has some invalid arguments_

The CSharpMigrationCodeGenerator should work more like the SqlServerMigrationSqlGenerator, where there is a virtual Generate method for MigrationOperation:
```
protected virtual void Generate(MigrationOperation migrationOperation)

```
As:
```
protected virtual void Generate(MigrationOperation migrationOperation, IndentedTextWriter writer)

```
In this way, developers could override this virtual method when creating a class that derives from CSharpMigrationCodeGenerator the same way it is currently possible with the SqlServerMigrationSqlGenerator class.

Without this, the workaround is to either reimplement the CSharpMigrationCodeGenerator or skip the code migration step for custom migration operations and translate each into a SqlOperation.

As a side note, since there is already a GetDefaultNamespaces virtual method, we can register any custom namespaces required to support the custom MigrationOperation types, so there is no issue with the migration class being generated with broken references.

-- Travis Schettler
↧
Search

Commented Unassigned: Allow generating migration code for a custom MigrationOperation from CSharpMigrationCodeGenerator [2799]

August 20, 2015, 9:36 am
$
0
0
Currently, the CSharpMigrationCodeGenerator must have a specific Generate method for each specific MigrationOperation in the migration. If there is a custom MigrationOperation in the list of migrations, it falls back to the Generate method for the AddColumnOperation, which fails with the following exception:

_The best overloaded method match for 'System.Data.Entity.Migrations.Design.CSharpMigrationCodeGenerator.Generate(System.Data.Entity.Migrations.Model.AddColumnOperation, System.Data.Entity.Migrations.Utilities.IndentedTextWriter)' has some invalid arguments_

The CSharpMigrationCodeGenerator should work more like the SqlServerMigrationSqlGenerator, where there is a virtual Generate method for MigrationOperation:
```
protected virtual void Generate(MigrationOperation migrationOperation)

```
As:
```
protected virtual void Generate(MigrationOperation migrationOperation, IndentedTextWriter writer)

```
In this way, developers could override this virtual method when creating a class that derives from CSharpMigrationCodeGenerator the same way it is currently possible with the SqlServerMigrationSqlGenerator class.

Without this, the workaround is to either reimplement the CSharpMigrationCodeGenerator or skip the code migration step for custom migration operations and translate each into a SqlOperation.

As a side note, since there is already a GetDefaultNamespaces virtual method, we can register any custom namespaces required to support the custom MigrationOperation types, so there is no issue with the migration class being generated with broken references.

-- Travis Schettler
Comments: RoMiller, I apologize, but maybe it's not clear what I'm asking for. I want to be able to allow generating the migration C# line of code for a custom MigrationOperation using the __CSharpMigrationCodeGenerator__. I want to be able to generate the custom migration operation instruction in the migration class itself, instead of having to edit it in there after the fact, or by using the workaround that I listed above. Your link is for the SqlServerMigrationSqlGenerator, which I am already using and have also referenced in my post above. This does create the SQL for a custom migration operation, but it does not account for adding the custom migration operation to the migration itself. I've already checked the code and there is definitely no way to do this currently, my post above is requesting that the CSharpMigrationCodeGenerator allows for this in the generated migration, jsut as the SqlServerMigrationSqlGenerator does in the generated SQL for the migration. -- Travis
↧
↧

Created Unassigned: Win8.1 / Win10 Entity framework not working at all [2803]

August 21, 2015, 3:46 am
$
0
0
I wanted to use EntityFramework on my Windows Universal app (Win10). So, I went to "Nuget package manager" and installed "Entity Framework 6.1.3" package. Installation was successfull, no errors occured. Then I've tried to create MyDbContext:DbContext class. I found that System.Data.Entities namespace is missing and I am not able to use Entity Framework at all.
In System.Data only System.Data.Common is present.
Same issue was present in Win8.1/Windows Phone 8.1 app.

Does Entity Framework supports Windows 10 apps and how to reach its classes?
↧

Created Unassigned: Migration commands fail for projects in a visual studio solution folder [2804]

August 21, 2015, 3:47 am
$
0
0
# Migration commands fail for projects in a visual studio solution folder
Functional impact

Migrations stop working as long as the project remains in the solution folder. The workaround of moving the project into the solution root, doing the migration and moving it back into the solution folder works, but isn't that obvious.

## Minimal repro steps

1. Create a project
1. Add nuget package for EF latest stable (6.1.3)
1. Enable migrations
1. Create a solution folder
1. Move the project into the solution folder
1. Try to add a migration


## Expected result

Migration is added

##Actual result

Command fails with the message The EntityFramework package is not installed on project ''.

↧

Commented Unassigned: Attribute uniqueidentifier PK with ROWGUIDCOL [2796]

August 21, 2015, 5:45 am
$
0
0
Hello!

If the PK is of type ROWGUIDCOL it should be attributed with ROWGUIDCOL in the synthesized SQL code.


Best regards,

Henrik Dahl

Comments: Hello Rowan! If I have this class: ``` public class HenrikDahlsClassForShowingRowanMiller { public Guid ID { get; set; } [Timestamp] public byte[] Version { get; set; } public Guid NonPKGuid { get; set; } } ``` EF currently generates this: ``` CREATE TABLE [NonSpecifiedSchema].[HenrikDahlsClassForShowingRowanMillers] ( [ID] [uniqueidentifier] NOT NULL DEFAULT newsequentialid(), [Version] rowversion NOT NULL, [NonPKGuid] [uniqueidentifier] NOT NULL, CONSTRAINT [PK_NonSpecifiedSchema.HenrikDahlsClassForShowingRowanMillers] PRIMARY KEY ([ID]) ) ``` As the PK is of type uniqueidentifier, the ROWGUIDCOL annotation should however better have been applied for the PK column, so this should preferably have been generated: ``` CREATE TABLE [NonSpecifiedSchema].[HenrikDahlsClassForShowingRowanMillers] ( [ID] [uniqueidentifier] NOT NULL ROWGUIDCOL DEFAULT newsequentialid(), [Version] rowversion NOT NULL, [NonPKGuid] [uniqueidentifier] NOT NULL, CONSTRAINT [PK_NonSpecifiedSchema.HenrikDahlsClassForShowingRowanMillers] PRIMARY KEY ([ID]) ) ``` [Documentation](https://msdn.microsoft.com/en-us/library/ms187742.aspx) Don't you agree? Best regards, Henrik Dahl
↧
↧

Edited Unassigned: Migration commands fail for projects in a visual studio solution folder [2804]

August 21, 2015, 6:05 am
$
0
0
# Migration commands fail for projects in a visual studio solution folder

## Functional impact

Migrations stop working as long as the project remains in the solution folder. The workaround of moving the project into the solution root, doing the migration and moving it back into the solution folder works, but isn't that obvious.

## Minimal repro steps

1. Create a project
1. Add nuget package for EF latest stable (6.1.3)
1. Enable migrations
1. Create a solution folder
1. Move the project into the solution folder
1. Try to add a migration


## Expected result

Migration is added

##Actual result

Command fails with the message The EntityFramework package is not installed on project ''.

↧

Created Unassigned: Introduce SparseAttribute attribute [2805]

August 21, 2015, 6:07 am
$
0
0
I would like to suggest introduction of a SparseAttribute, like if I have this code:

```
public class HenrikDahlsClassForShowingRowanMiller
{
public Guid ID { get; set; }

[Timestamp]
public byte[] Version { get; set; }

[Sparse]
public Guid? NonPKGuid { get; set; }
}

```
This SQL should be generated:
```
CREATE TABLE [NonSpecifiedSchema].[HenrikDahlsClassForShowingRowanMillers] (
[ID] [uniqueidentifier] ROWGUIDCOL NOT NULL DEFAULT newsequentialid(),
[Version] rowversion NOT NULL,
[NonPKGuid] [uniqueidentifier] SPARSE,
CONSTRAINT [PK_NonSpecifiedSchema.HenrikDahlsClassForShowingRowanMillers] PRIMARY KEY ([ID])
)
```
[Documentation](https://msdn.microsoft.com/en-us/library/cc280604(v=sql.120).aspx)


Best regards,

Henrik Dahl

↧

Commented Unassigned: 6.1.3 Inheritance Bug (6.1.1 works fine) [2798]

August 21, 2015, 6:36 am
$
0
0
With this model

public class Class1
{
[Key]
public int Id { get; set; }

public virtual string MyProperty { get; set; }
// other properties
}

public class Class3 : Class1
{
[Required]
public override string MyProperty { get; set; }

public string Class3Prop { get; set; }
}


public class TestContext : DbContext
{
public TestContext(DbConnection connection) : base(connection, true) { }

public DbSet<Class1> C1s { get; set; }
public DbSet<Class3> C3s { get; set; }


}

I expect that Class3.MyProperty is required and Class1.MyProperty is not required.

With EF 6.1.1 everything's working fine (in SQL Server the MyProperty field is nullable).
With EF 6.1.3 both Class3.MyProperty and Class1.MyProperty are interpreted as Required (and in SQL Server MyProperty field is not nullable)

Comments: Hi Rowan, actually 6.1.1 worked in a little different way or at least, if there is only one metadata model entry for MyProperty, the MyProperty is configured in the right way in 6.1.1 (on DB MyProperty nullability should be the less restrictive and so it is in EF 6.1.1) and 6.1.1 does not use the metadata model to perform checks on SaveChanges (it checks for MyProperty null via code only on Class3 because on Class1 MyProperty can be nullable). Look at this test. public static void Run(DbConnection connection) { using (TestContext db = new TestContext(connection)) { // MyProperty not specified db.C1s.Add(new Class1()); db.SaveChanges(); // MyProperty not specified db.C3s.Add(new Class3()); db.SaveChanges(); } } __With EF 6.1.1__ The field on database was created as not nullable. The piece of code above raised an exception on the second SaveChanges (probably it is an EF check not a DBMS check) and is right becouse in Class3 MyProperty is Required. The first SaveChanges worked fine because MyProperty in Class1 is not required. So, about your answer, you picked up the attributes in the right way (Class1.MyProperty not required, Class3.MyProperty required). Probably in the metadata model you get the less restrictive but then, when you check entities on SaveChanges, you get the proper one. __With EF 6.1.3__ The exception is raised on the first SaveChanges. About the test you requested (configure everything via fluent interface) I think that in EF 6.x there is not an IsRequired overload with 1 parameter (same as RequiredAttribute).
↧
Search

Commented Feature: UpForGrabs: Add David Roth's "EdmxReader" into EF6 code first to improve startup time by caching DbCompiledModel to disk [2631]

August 21, 2015, 9:53 am
$
0
0
My code first DbContext has ~300 entities and takes ~20 seconds to initialize on startup (even after EFInteractiveViews installed).

It greatly improves the startup time (20 seconds down to 4.5 seconds) if I pass a DbCompiledModel into the first DbContext constructor:

var firstDbContext = new DbContext(connectionString, myDbCompiledModel);

There is no way to create a DbCompiledModel in the main library, but I have done it successfully using David Roth's branch of EF with DbModelStore:

http://www.fusonic.net/en/blog/2014/07/09/three-steps-for-fast-entityframework-6.1-first-query-performance/
https://github.com/davidroth/entityframework/tree/DbModelStore

I demonstrated this improvement using David's recommended method in the bloc above, but also by directly using his EdmxReader utility to import a file generated earlier by EdmxWriter:

// on first run
var db = new DbContext(connectionString);
var xml = XmlWriter.Create(new FileStream(@"C:\temp\efcache\myEdmx.xml", FileMode.OpenOrCreate));
EdmxWriter.WriteEdmx(db, xml)

// on next run - use EdmxReader!
var dbCompiledModel = EdmxReader.Read(XmlReader.Create(new FileStream(@"C:\temp\efcache\myEdmx.xml", FileMode.Open)), "...");
var db = new DbContext(connectionString, dbCompiledModel); /// MUCH FASTER!

Clearly the technique is possible, but requires changes to the EF core library. Delighted as I am with David's branch, I am reluctant to introduce an unsupported EF branch into a production environment.

Introducing an EdmxReader into the main trunk would address my concerns, and allow me to greatly improve startup time.
Comments: @RoMiller, what would it take to get this implemented for a future release of EF 6.1? Are you just waiting on a pull request?
↧
↧

Edited Issue: Migration commands fail for projects in a visual studio solution folder [2804]

August 21, 2015, 11:45 am
$
0
0
# Migration commands fail for projects in a visual studio solution folder

## Functional impact

Migrations stop working as long as the project remains in the solution folder. The workaround of moving the project into the solution root, doing the migration and moving it back into the solution folder works, but isn't that obvious.

## Minimal repro steps

1. Create a project
1. Add nuget package for EF latest stable (6.1.3)
1. Enable migrations
1. Create a solution folder
1. Move the project into the solution folder
1. Try to add a migration


## Expected result

Migration is added

##Actual result

Command fails with the message The EntityFramework package is not installed on project ''.

↧

Edited Unassigned: IEnumerable projections are assigned a list and then the list mutated [2802]

August 21, 2015, 11:49 am
$
0
0
Consider the following classes:

public class Test {

public IEnumerable<Container> Fake {
get {
return Real.Select(e => new Container { Item1 = e.Item1 });
}
set {
Real = new List<Tuple<int>>(value.Select(p => new Tuple<int>(p.Item1)));
}
}

public List<Tuple<int>> Real { get; set; }
}

public class Container {
public int Item1 { get; set; }
}

And the following query:

from a in Something
group a by a.Field into g
select new Test {
Fake = g.Select(a => new Container { Item1 = a.Id })
}

The result is a quite surprising empty `Fake` and `Real` Properties. Stepping in the debugger suggests that EF assigns a list to Fake, and then tries to add elements to that reference, which of course fails in this setting.

The same query works when executed over Linq to Sql.

EF should populate the list and then assign it. It should not assume the stored object will persist.
↧

Closed Unassigned: System.Data.Entity Dependant on Microsoft.Office.Interop.Word and Microsoft.DirectX.DirectSound [2793]

August 21, 2015, 11:52 am
$
0
0
I developed an application using framework 3.5 and my application fails if Microsoft.Office.Interop.Word.dll or Microsoft.DirectX.DirectSound.dll were not found.

Fuslog shows that the calling assembly for those dlls is System.Data.Entity as below:

*** Assembly Binder Log Entry (8/6/2015 @ 11:35:19 PM) ***

The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file specified.

Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable d:\build\Pacs_Integ\bin\release\MedStreaming.Client.exe
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: User = WIN-8CA5GMGURLD\Administrator
LOG: DisplayName = Microsoft.DirectX.DirectSound, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
(Fully-specified)
LOG: Appbase = file:///d:/build/Pacs_Integ/bin/release/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.
===
LOG: Start binding of native image Microsoft.DirectX.DirectSound, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
WRN: No matching native image found.

I tried to create another simple project that uses Sytem.Data.Entity.dll and it did not call these dlls, I cannot find why these dlls called by my application!

Is there a way to decouple my application from these dlls?
Comments: Closing as we have not heard back with requested details
↧

Commented Unassigned: Entities materialized by SqlQuery don't display lazy loading [2790]

August 23, 2015, 4:30 am
$
0
0
Compare these two snippets (in Linqpad, connected to a DbContext):

```
var prd1 = this.Database.SqlQuery<Product>("Select * From Product").First();
Entry(prd1).State.Dump(); // Detached
prd1.Categories.Dump(); // (0 items)
```
And
```
var prd2 = Products.AsNoTracking().ToArray().First();
Entry(prd2).State.Dump(); // Detached
prd2.Categories.Dump(); // (2 items)
```
In both snippets, `prd` and `prd2` are proxy objects. Still, in the first snippet lazy loading is not triggered, whereas in the second, it is. This also shows in the executed queries.

When in the first snippet the `prd1` object is attached to the context as `Unchanged` lazy loading _does_ occur.

I think this is inconsistent behavior. If a proxy is materialized by any EF process, I think it should be capable of lazy loading.

Probably related: the entities from `SqlQuery` don't respond to relationship fixup either. If they have `Categories` collections in a 1:n association, these won't be populated if the belonging categories are loaded separately by a `Load` statement.

(EF 6.1.3, .Net 4.0).
Comments: I don't know if lazy loading _should_ be allowed. Maybe it's enough to remove the expectation of it to happen by materializing the entity as a simple POCO, not a proxy.
↧
↧

Created Unassigned: Enable Migrations in MVC throws File not Found Error [2806]

August 24, 2015, 2:04 am
$
0
0
I'm new to using MVC, and when working through the tutorials regarding migrations in Visual Studio 2013 I appear to have broken the tie-in to EntityFramework in the Package Manager console.

I believe this started when I updated the EntityFramework to version 6.1.3, But that appears to be incompatible with the MVC Controller scaffolding. So I rolled it back to version 5.0.0.

When I now enter the command

```
enable-migrations
```

I get the following error:

```
Exception calling "CreateInstanceFrom" with "8" argument(s): "Could not load file or assembly 'EntityFramework, Version=5.0.0.0 , Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified." At D:\ss\CAP\CAP_MVC_Dev_2\CAP_MVC\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:431 char:31 + $domain.CreateInstanceFrom <<<< ( + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : DotNetMethodTargetInvocation
```

The file ```EntityFramework.psm1``` exists where it is described above, but the error appears to be in that file? How is ```$domain.CreateInstanceFrom``` missing, and where from? Uninstalling and reinstalling the EntityFramework package makes no difference.

I've tried creating new projects from scratch and this error persists across them. An uninstall/reinstall of Visual Studio 2013 has not resolved the issue either, nor has destroying the connected database and starting again with an empty one.
↧

Edited Unassigned: Enable Migrations in MVC throws File not Found Error [2806]

August 24, 2015, 2:04 am
$
0
0
I'm new to using MVC, and when working through the tutorials regarding migrations in Visual Studio 2013 I appear to have broken the tie-in to EntityFramework in the Package Manager console.

I believe this started when I updated the EntityFramework to version 6.1.3, But that appears to be incompatible with the MVC Controller scaffolding. So I rolled it back to version 5.0.0.

When I now enter the command ```enable-migrations```

I get the following error:

```
Exception calling "CreateInstanceFrom" with "8" argument(s): "Could not load file or assembly 'EntityFramework, Version=5.0.0.0 , Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified." At D:\ss\CAP\CAP_MVC_Dev_2\CAP_MVC\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:431 char:31 + $domain.CreateInstanceFrom <<<< ( + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : DotNetMethodTargetInvocation
```

The file ```EntityFramework.psm1``` exists where it is described above, but the error appears to be in that file? How is ```$domain.CreateInstanceFrom``` missing, and where from? Uninstalling and reinstalling the EntityFramework package makes no difference.

I've tried creating new projects from scratch and this error persists across them. An uninstall/reinstall of Visual Studio 2013 has not resolved the issue either, nor has destroying the connected database and starting again with an empty one.
↧
Search

Edited Unassigned: Enable Migrations in MVC throws File not Found Error [2806]

August 24, 2015, 2:05 am
$
0
0
I'm new to using MVC, and when working through the tutorials regarding migrations in Visual Studio 2013 I appear to have broken the tie-in to EntityFramework in the Package Manager console.

I believe this started when I updated the EntityFramework to version 6.1.3, But that appears to be incompatible with the MVC Controller scaffolding. So I rolled it back to version 5.0.0.

When I now enter the command ```enable-migrations```

I get the following error:

```
Exception calling "CreateInstanceFrom" with "8" argument(s): "Could not load file or assembly 'EntityFramework, Version=5.0.0.0 , Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified."
At D:\ss\CAP\CAP_MVC_Dev_2\CAP_MVC\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:431 char:31
+ $domain.CreateInstanceFrom <<<< (
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodTargetInvocation
```

The file ```EntityFramework.psm1``` exists where it is described above, but the error appears to be in that file? How is ```$domain.CreateInstanceFrom``` missing, and where from? Uninstalling and reinstalling the EntityFramework package makes no difference.

I've tried creating new projects from scratch and this error persists across them. An uninstall/reinstall of Visual Studio 2013 has not resolved the issue either, nor has destroying the connected database and starting again with an empty one.
↧

Commented Issue: Can't map two classes with same name from different namespace [483]

August 25, 2015, 5:47 am
$
0
0
EF doesn't allow two classes with the same name, but different namespaces, to be mapped.

This is complex to change so we also have an item to provide a better exception message until this is supported - http://entityframework.codeplex.com/workitem/589

namespace Test.Security
{
public class Question
{
public Guid Id { get; set; }
}
}

namespace Test.Forms
{
public class Question
{
public Guid Id { get; set; }
}
}

Comments: I have a project with 3 modules, which share class names, mapped under different SQL schemas. All went fine and dandy (except the fact that you can enable migrations on a single context) with the Code First implementation, until I've hit the aforementioned problem. Thanks Microsoft, next time I'll think twice before choosing EF against NHibernate.
↧
↧

Created Unassigned: Migrationing from EF5 to 6.1.2 fails for SqlCE (follow-up on #2659) [2807]

August 25, 2015, 7:04 am
$
0
0
Reporting this to note that [work item #2659](https://entityframework.codeplex.com/workitem/2659) has __not__ been resolved for all use cases.

We ship a desktop application using EF and SQL CE and perform migrations programmatically as needed - we can't easily perform a disjointed upgrade (going from 5 to 6 to 6.1.2, migrating at each step) as the work item resolution suggests. It would be much more more helpful if the migration table code was updated to cover all historical scenarios.

It looks like I'll have to stick with EF 5.0.0 until there are newer versions that can actually cleanly support upgrading.
↧

Created Unassigned: The StringLengthAttribute is not honoring MinimumLength [2808]

August 25, 2015, 7:03 pm
$
0
0
I have a simple code-first project. In one of the POCO objects, I have the following property:

```
[Required]
[StringLength(3, MinimumLength = 3)]
public string TestString { get; set; }
```
I expected the Add-Migration command to create the following output:
```
TestString = c.String(nullable: false, maxLength: 3, fixedLength: true),
```
However, I get the following output:
```
TestString = c.String(nullable: false, maxLength: 3),
```
I've check the StringLengthAttribute for any property that would allow me to specify a fix length but there isn't any. Therefore, (IMHO) FixedLength should be set using code something like this:

```
FixedLength = MaximumLength == MinimumLength;
```

↧

Commented Issue: UpForGrabs: Entity Framework Designer fails calling sp_executesql with too many parameters when updating large model from database [520]

August 26, 2015, 2:49 am
$
0
0
We recently upgraded to VS 2012 (still targeting .net 4.0) so we could use the new model diagrams to support having a larger merged data model. We were able to merge our models by hand into one combined model and can use it without issue at runtime (402 tables with lots of associations).

However when I try to update the model from the database, the designer gets an error:

Error 3 An error occurred while executing the command definition. See the inner exception for details.
The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.

SQL Server (2008 r2) has a fixed limit of 2100 parameters that can be passed to a stored procedure. EF is using a call to sp_executesql where it is passing 2400 parameters. While debugging the exeception in visual studio, we saw may duplicates like using one parameter for each table for the catalog, the schema and the table name rather than reusing the catalog and schema parms (that alone would've kept the call under the limit). Here's an example (notice each SchemaName has a different parm for a value that can't be different since you don't support mutliple databases in the same edmx!):

WHERE (([Extent1].[CatalogName] LIKE @p0) AND ([Extent1].[SchemaName] LIKE @p1) AND ([Extent1].[Name] LIKE @p2)) OR

(([Extent1].[CatalogName] LIKE @p3) AND ([Extent1].[SchemaName] LIKE @p4) AND ([Extent1].[Name] LIKE @p5)) OR (([Extent1].

[CatalogName] LIKE @p6) AND ([Extent1].[SchemaName] LIKE @p7) AND ([Extent1].[Name] LIKE @p8)) OR (([Extent1].[CatalogName]

LIKE @p9) AND ([Extent1].[SchemaName] LIKE @p10) AND ([Extent1].[Name] LIKE @p11)) OR (([Extent1].[CatalogName] LIKE @p12)

AND ([Extent1].[SchemaName] LIKE @p13) AND ([Extent1].[Name] LIKE @p14)) OR (([Extent1].[CatalogName] LIKE @p15) AND

([Extent1].[SchemaName] LIKE @p16) AND ([Extent1].[Name] LIKE @p17)) OR (([Extent1].[CatalogName] LIKE @p18) AND ([Extent1].

[SchemaName] LIKE @p19) AND ([Extent1].[Name] LIKE @p20)) OR (([Extent1].[CatalogName] LIKE @p21) AND ([Extent1].

[SchemaName] LIKE @p22) AND ([Extent1].[Name] LIKE @p23)) OR (([Extent1].[CatalogName] LIKE @p24) AND ([Extent1].

[SchemaName] LIKE @p25) AND ([Extent1].[Name] LIKE @p26)) OR (([Extent1].[CatalogName] LIKE @p27) AND ([Extent1].

[SchemaName] LIKE @p28) AND ([Extent1].[Name] LIKE @p29)) OR (([Extent1].[CatalogName] LIKE @p30) AND ([Extent1].

[SchemaName] LIKE @p31) AND ([Extent1].[Name] LIKE @p32)) OR (([Extent1].[CatalogName] LIKE @p33) AND ([Extent1].

[SchemaName] LIKE @p34) AND ([Extent1].[Name] LIKE @p35)) OR (([Extent1].[CatalogName] LIKE @p36) AND ([Extent1].

[SchemaName] LIKE @p37) AND ([Extent1].[Name] LIKE @p38)) OR (([Extent1].[CatalogName] LIKE @p39) AND ([Extent1].

[SchemaName] LIKE @p40) AND ([Extent1].[Name] LIKE @p41)) OR (([Extent1].[CatalogName] LIKE @p42) AND ([Extent1].

[SchemaName] LIKE @p43) AND ([Extent1].[Name] LIKE @p44)) OR (([Extent1].[CatalogName] LIKE @p45) AND ([Extent1].

[SchemaName] LIKE @p46) AND ([Extent1].[Name] LIKE @p47)) OR (([Extent1].[CatalogName] LIKE @p48) AND ([Extent1].


See more on this post: http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/aafb63c4-61df-4d8d-9373-df78d6f7d686/
Comments: Same here, we are live attempting to do a bug fix and ran into this problem. How have others got round this issue?
↧
Viewing all 9566 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>