Databases
StackOverflow2013
Postsdbo
POIndex already exists error in EF 4.3 Code First with Data Annotations
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIndex already exists error in EF 4.3 Code First with Data Annotations
    primarykey
    data
    text
    <p>I'm trying to create a billing database with Entity Framework 4.3 using Code First with Data Annotations, and I'm getting an error every time I try to create my database. Here are the objects that I'm dealing with:</p> <pre><code>public class ClientBase { [Key, DatabaseGenerated(DatabaseGeneratedOption.Identity)] public int ClientID { get; set; } [Required] public string ClientName { get; set; } [Required] public bool IsActive { get; set; } [Required] public string ClientContactName { get; set; } [Required] public string ClientContactEmail { get; set; } public virtual List&lt;PropertyBase&gt; Communities { get; set; } } public class PropertyBase { [Key, DatabaseGenerated(DatabaseGeneratedOption.Identity)] public int PropertyID { get; set; } [ForeignKey("Client")] public int ClientID { get; set; } [Required, EnumDataType(typeof(BillingFrequency))] public BillingFrequency PropertyBillingFrequency { get; set; } [Required] public bool IsActive { get; set; } [Required] public string PropertyName { get; set; } public string PropertyStreet { get; set; } public string PropertyCity { get; set; } public string PropertyState { get; set; } public int PropertyZipCode { get; set; } public virtual ClientBase Client { get; set; } } </code></pre> <p>No matter what I try to do, I always get this error: </p> <pre><code>The operation failed because an index or statistics with name 'IX_ClientID' already exists on table 'Property'. </code></pre> <p>I've seen solutions to this question with the Fluent API, but I haven't found one for Data Annotations.</p> <p>Does anyone have any idea how to fix this?</p> <p>EDIT: Here is the code in the DbContext:</p> <pre><code>public DbSet&lt;ClientBase&gt; ClientBases { get; set; } public DbSet&lt;PropertyBase&gt; PropertyBases { get; set; } protected override void OnModelCreating(DbModelBuilder modelBuilder) { modelBuilder.Conventions.Remove&lt;PluralizingTableNameConvention&gt;(); base.OnModelCreating(modelBuilder); } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USIronMan84
    1. USIronMan84
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIndex already exists error in EF 4.3 Code First with Data Annotations
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt all works for me. I don't understand where *table 'Property'* is coming from in this configuration.
      singulars
      1. POIndex already exists error in EF 4.3 Code First with Data Annotations
      1. UStzerb
    2. COYikes! I forgot to put [Table("Property")] over the PropertyBase class.
      singulars
      1. POIndex already exists error in EF 4.3 Code First with Data Annotations
      1. USIronMan84
    3. COCould there be a trigger running on the SQL server that created the Index? I have no idea where it (even the first one) would be coming from.
      singulars
      1. POIndex already exists error in EF 4.3 Code First with Data Annotations
      1. UStzerb
 

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