Home / Questions / 335894
Accepted
Edwin Romero
Asked: 2020-03-11 03:21:49 +0800 CST 2020-03-11 03:21:49 +0800 CST

In DataAnnotation how do I tell it is a view?

  • 772

I normally use this notation to define my tables

namespace domain.Entities
{
     [Table("seg_modulos")]
     public class modulo
     {
          [Column("modID")]
          [Key]
          public int modID { get; set; }

          [Column("modulo")]
          public string modname { get; set; }
     }
}

but the ContextBase requires me for some unknown reason that I have a [KEY] to be able to do the dbset

  public DbSet<modulo> modulo { get; set; }

For security purposes in my system I want to call a view, it will only make queries, is there a tag like TABLE in DataAnotation, View does not work for me, does anyone know what it is or an alternative way to do it?

thanks if I find out before I post the answer greetings to the community

c#

1 Answers

  1. Best Answer

    Alright there is no such thing as a Data annotation for view so I found the way to do it eye this for asp core 3.x EF Core.

    1) The first because it gives me an error if I don't define a KEY

    public DbSet<modulo> modulo { get; set; }

    because the EF automatically looks for an ID so in the views it does it too and that's why it gave me an error that there was no ID. So what we have to do is the following: 2) We create the entity without data annotation

    namespace domain.Entities
{
     public class permisosview
     {

          public int rolID { get; set; }
          public string rol { get; set; }
          public string modulo { get; set; }
          public int passmodID { get; set; }
          public string submodulo { get; set; }
          public int submodID { get; set; }
          public int passtaskID { get; set; }
          public string tarea { get; set; }

     }
}

    Then in the Dbcontext we must tell it that it is a view not a table and we do that by modifying the OnModelCreating

      protected override void OnModelCreating(ModelBuilder modelBuilder)
  {
       modelBuilder
           .Entity<permisosview>(pv =>
           {
                pv.HasNoKey();
                pv.ToView("rol_permisos_view");
                pv.Property(v => v.rolID).HasColumnName("rolID");
                pv.Property(v => v.rol).HasColumnName("rol");
                pv.Property(v => v.modulo).HasColumnName("modulo");
                pv.Property(v => v.passmodID).HasColumnName("passmodID");
                pv.Property(v => v.submodulo).HasColumnName("submodulo");
                pv.Property(v => v.submodID).HasColumnName("submodID");
                pv.Property(v => v.passtaskID).HasColumnName("passtaskID");
                pv.Property(v => v.tarea).HasColumnName("tarea");
           });
  }

    You can see that for the view "permisosview" we don't tell it that there is no key "HasNoKey" and we define the columns and the name of the view in the database. now we can easily use the dbset

    public DbSet<permisosview> permisos { get; set; }

    and Well that's how we use views with EF Core 3.x for 2.x it's different "DbQuery" is used I hope someone helps greetings

    • 0