Generic dbset<T> table name property

Question

1.00/5 (1 vote)

See more:

Please how do I assign table name to generic DBSet<t> base on Model?
I want to create a table for every registered user, using their userId and the table name in EF6.

public class ContactModel
    {
        [Key]
        [Required]
        [MaxLength(20), MinLength(6)]
        public string Phone { get; set; }
        [MaxLength(45), MinLength(2)]
        public string Name { get; set; }
        [MaxLength(100)]
        public string Email { get; set; }
        
    }

What I have tried:

[Table("Logedin Userid")]
public class ContactModel
    {
        [Key]
        [Required]
        [MaxLength(20), MinLength(6)]
        public string Phone { get; set; }
        [MaxLength(45), MinLength(2)]
        public string Name { get; set; }
        [MaxLength(100)]
        public string Email { get; set; }
        
    }

Posted 10-Jun-20 13:44pm

Enobong Adahada

Updated 10-Jun-20 23:19pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Accepted Answer · 2020-06-10T23:19:00

That's a terrible idea!

Create a single table for your contacts, and add a foreign key relationship with the users table.

C#

public class User
{
    [Key]
    public Guid Id { get; set; }
    
    public virtual IList<Contact> Contacts { get; set; }
    
    ... Other properties ...
}

public class Contact
{
    [Key]
    public Guid Id { get; set; }
    
    public Guid UserId { get; set; }
    
    public virtual User User { get; set; }
    
    [Required]
    [MaxLength(20), MinLength(6)]
    public string Phone { get; set; }
    
    [MaxLength(45), MinLength(2)]
    public string Name { get; set; }
    
    [MaxLength(100)]
    public string Email { get; set; }
}

Relationships, navigation properties, and foreign keys - EF6 | Microsoft Docs[^]

You'll also want to check your [Key] definition - most systems allow multiple contacts with the same telephone number, even for the same parent entity. If you really want a unique telephone number per user, then create a composite key.

C#

public class Contact
{
    [Key, Column(Order = 0)]
    public Guid UserId { get; set; }
    
    public virtual User User { get; set; }
    
    [Required]
    [MaxLength(20), MinLength(6)]
    [Key, Column(Order = 1)]
    public string Phone { get; set; }
    
    ... Other properties ...
}

Composite Keys - Code First Data Annotations - EF6 | Microsoft Docs[^]