Databases
StackOverflow2013
Postsdbo
POUsers with different capabilities
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsers with different capabilities
    primarykey
    data
    text
    <p>I'm creating an ASP.Net MVC 5 application. In my website, 3 different types of users exist.</p> <ul> <li>Admin</li> <li>Normal users</li> <li>Restaurants</li> </ul> <p>Each of these users have its own capabilities and access rights. Meaning, the view for each of them should be different.</p> <p>I have created the models for both of the normal and restaurant. I was wondering how I can modify my existing structure to support this functionality.</p> <pre><code>public class User : IUser { public User() : this(String.Empty) { } public User(string userName) { UserName = userName; Id = Guid.NewGuid().ToString(); } [Key] public string Id { get; set; } [Required] public string UserName { get; set; } [Required] public string FirstName { get; set; } [Required] public string LastName { get; set; } public string Phone { get; set; } public string MobilePhone { get; set; } [Required] [DataType(DataType.EmailAddress)] public string Email { get; set; } public virtual IList&lt;UserAddress&gt; Addresses { get; set; } } public class Restaurant { [Key] public int ID { get; set; } [Required] public string Name { get; set; } public virtual IList&lt;RestaurantAddress&gt; Addresses { get; set; } public virtual IList&lt;RestaurantFood&gt; Menu { get; set; } public virtual IList&lt;Review&gt; Reviews { get; set; } [DataType(DataType.Url)] public string Website { get; set; } [DataType(DataType.PhoneNumber)] public string Phone { get; set; } [DataType(DataType.PhoneNumber)] public string Fax { get; set; } [DataType(DataType.EmailAddress)] public string Email { get; set; } public int Seats { get; set; } public double AverageRating { get; set; } public double AveragePrice { get; set; } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USAlireza Noori
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsers with different capabilities
      1. USSirwan Afifi
      1. VTFavorite
    2. VO
      singulars
      1. POUsers with different capabilities
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUsers with different capabilities
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO[this](http://www.dotnettips.info/post/1166/%D9%85%D8%AF%DB%8C%D8%B1%DB%8C%D8%AA-%D8%B3%D9%81%D8%A7%D8%B1%D8%B4%DB%8C-%D8%B3%D8%B7%D9%88%D8%AD-%D8%AF%D8%B3%D8%AA%D8%B1%D8%B3%DB%8C-%DA%A9%D8%A7%D8%B1%D8%A8%D8%B1%D8%A7%D9%86-%D8%AF%D8%B1-mvc) post can be helpful
      singulars
      1. POUsers with different capabilities
      1. USSirwan Afifi
    2. CO@SirwanAfifi Thanks. It was helpful to some extent. I'll have to look for some more. My problem is this: what is the best way to change the existing models to add support for this flexibility. Should I add all the info to the `User` model? Should I add the foreign key to the `User` model? I want to integrate the additional info in the model.
      singulars
      1. POUsers with different capabilities
      1. USAlireza Noori
    3. CO@AlirezaNoori I have updated my answer, which can give you exact details as to how to go about implementing it. You don't necessarily need ASP Security Kit, if you can spend lots of hours to figure out the implementation.
      singulars
      1. POUsers with different capabilities
      1. USVarun K
 

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