13 comments

Add a comment…

Sign in

prestine

Your name

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Michael Bisbjerg commented  ·  November 27, 2013 5:39 PM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  [Index(Column = 0, Name = "IX_MyIndex")]
  [Index(Column = 1, Name = "IX_MyIndex")]
  [Index(Column = 2, Name = "IX_MyIndex")]

  Remember column ordering, people :)

• Karl Dodd commented  ·  June 27, 2013 7:38 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Learn from the XBOX team and listen to the users. plz.

• Jim Wolff commented  ·  May 14, 2013 3:55 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I forgot to add, it is easily possible via code first migrations, but having the attribute or the fluent api would make auto generation of the index possible when making the migration.

• Jim Wolff commented  ·  May 14, 2013 3:53 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  There are several suggestions on this in a question i posted on stackoverflow on the subject:

  http://stackoverflow.com/questions/8262590/entity-framework-code-first-fluent-api-adding-indexes-to-columns

  I think EF needs to have both an index attribute and a way to configure it via EntityTypeConfigurations and the fluent api.

• Marc commented  ·  February 26, 2013 2:30 PM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Agreed, but can we not forget about the designer please? Some of us actually prefer model first!

  The ability to generate indexes on a column is needed, but also a way of setting it from the designer.

• Kevin Piette commented  ·  October 24, 2012 7:54 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  As a workaround we've been adding unique and non-unique indexes to the migrations (using the fluent Index() methods supported for migrations). Sort-order support requires other ModelBuilder specializations described elsewhere.

  This isn't ideal since the manual mods are lost during development if the migration is regenerated but at least allows the indexes to be reflected in code.

• Ken Demarest commented  ·  October 24, 2012 7:32 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Lack of ability to use Annotations or Fluent to create indexes is a black mark on the entire Entity Framework team. Do you think ANYONE writing code doesn't need to add indexes? Really?

• Элькенос commented  ·  October 2, 2012 8:08 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  More once: included columns if it possible.

  e.g.:

  [Indexed]
  [IncludedColumn("Name")]
  public long Id { get; set; }
  public string Name { get; set; }

• Anonymous commented  ·  August 12, 2012 9:11 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Only one thing - this SHOULD be in the FluentAPI only, not in Attribues. Because it's SQL-dependend and you should not mix it with model.

• HOONS commented  ·  June 11, 2012 10:30 PM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It would be helpful, if EF could attach Unique and Clustered options.
  like bellow:

  [Indexed(Unique=false,Clustered=false)]
  int A { get; set; }

• Ricardo Peres commented  ·  March 5, 2012 7:09 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I agree this is a must have!
  Other required properties:

  - Clustered/unclustered;
  - Unique;
  - Group name (to allow indexes over many properties; if it is empty, it applies to just the property where it is declared; if it is not empty, all properties with the same group name are added to the index definition.

  This has some problems, however:

  - The actual column name may be explicitly defined in configuration by code;
  - The actual SQL to use for index creation depends on the current DB engine.

  Hope the Entity Framework team can do something about these problems, this is quite necessary!

• John Galt commented  ·  February 24, 2012 6:17 AM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This should also be added to Fluent API so that we can create composite indexes as needed as well.

  The only other thing that needs to be added is an SQL Specific annotation for FileTables and Filestreams!

• mousedoc commented  ·  October 12, 2011 4:41 PM  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is drastically needed to prevent having to manually modify auto-generated migration code that can be wiped out when starting over on a new database.