NetCore+Dapper WebApi架構搭建（三）：添加實體和倉儲

上一節講了類庫添加一些底層的基本封裝，下面來添加實體和倉儲

1、Entities文件夾添加一個實體類Users，繼承BaseModel，即擁有BaseModel的主鍵

using System;

namespace Dinner.Dapper.Entities
{
    public class Users : BaseModel
    {
        /// <summary>
        /// 用戶名
        /// </summary>
        public string UserName { get; set; }

        /// <summary>
        /// 密碼
        /// </summary>
        public string Password { get; set; }

        /// <summary>
        /// 性別（0女，1男）
        /// </summary>
        public int Gender { get; set; }

        /// <summary>
        /// 出生年月日
        /// </summary>
        public DateTime Birthday { get; set; }

        /// <summary>
        /// 創建日期
        /// </summary>
        public DateTime CreateDate { get; set; }

        /// <summary>
        /// 是否刪除（0正常，1刪除）
        /// </summary>
        public int IsDelete { get; set; }
    }
}

2、IRepository中添加一個IUsersRepository倉儲接口，注意倉儲接口的寫法規范 I+實體名+Repository，對應的倉儲業寫法貴方 實體名+Repository，這么寫不僅是日常規范更是為后面的依賴注入做鋪墊

繼承自IRepositoryBase<Users> 這個泛型接口，如果你還要定義其他操作，應該自定義接口的新操作方法，然后在實現類中實現自定義的方法

using Dinner.Dapper.Entities;
using System;
using System.Collections.Generic;
using System.Threading.Tasks;

namespace Dinner.Dapper.IRepository
{
    public interface IUserRepository : IRepositoryBase<Users> 
    {
        #region 擴展的dapper操作

        //加一個帶參數的存儲過程
        string ExecExecQueryParamSP(string spName, string name, int Id);

        Task<List<Users>> GetUsers();

        Task PostUser(Users entity);

        Task PutUser(Users entity);

        Task DeleteUser(Guid Id);

        Task<Users> GetUserDetail(Guid Id);

        #endregion
    }
}

3、Repository中添加一個UserRepository接口實現類繼承自RepositoryBase<Users>, IUserRepository

using Dapper;
using Dinner.Dapper.Entities;
using Dinner.Dapper.IRepository;
using System;
using System.Collections.Generic;
using System.Data;
using System.Threading.Tasks;

namespace Dinner.Dapper.Repository
{
    public class UserRepository : RepositoryBase<Users>, IUserRepository
    {
        public async Task DeleteUser(Guid Id)
        {
            string deleteSql = "DELETE FROM [dbo].[Users] WHERE Id=@Id";
            await Delete(Id, deleteSql);
        }

        public string ExecExecQueryParamSP(string spName, string name, int Id)
        {
            using (IDbConnection conn = DataBaseConfig.GetSqlConnection())
            {
                DynamicParameters parameters = new DynamicParameters();
                parameters.Add("@UserName", name, DbType.String, ParameterDirection.Output, 100);
                parameters.Add("@Id", Id, DbType.String, ParameterDirection.Input);
                conn.Execute(spName, parameters, null, null, CommandType.StoredProcedure);
                string strUserName = parameters.Get<string>("@UserName");
                return strUserName;
            }
        }

        public async Task<Users> GetUserDetail(Guid Id)
        {
            string detailSql = @"SELECT Id, UserName, Password, Gender, Birthday, CreateDate, IsDelete FROM [dbo].[Users] WHERE Id=@Id";
            return await Detail(Id, detailSql);
        }

        public async Task<List<Users>> GetUsers()
        {
            string selectSql = @"SELECT Id, UserName, Password, Gender, Birthday, CreateDate, IsDelete FROM [dbo].[Users]";
            return await Select(selectSql);
        }

        public async Task PostUser(Users entity)
        {
            string insertSql = @"INSERT INTO [dbo].[Users](Id, UserName, Password, Gender, Birthday, CreateDate, IsDelete) VALUES(@Id, @UserName, @Password, @Gender, @Birthday, @CreateDate, @IsDelete)";
            await Insert(entity, insertSql);
        }

        public async Task PutUser(Users entity)
        {
            string updateSql = "UPDATE [dbo].[Users] SET UserName=@UserName, Password=@Password, Gender=@Gender, Birthday=@Birthday, CreateDate=@CreateDate, IsDelete=@IsDelete WHERE Id=@Id";
            await Update(entity, updateSql);
        }
    }
}

Dapper就是寫純Sql語句的，這很考驗Sql功底，不像EF那樣，寫幾個Linq就解決了，不過視圖，函數，存儲過程都是通用的，Dapper可以，EF也可以

這個Dapper的數據庫和表需要你自己創建，不比EF可以自動生成

上面建的實體，倉儲接口和倉儲實現都是為了演示而已，你們若想添加其他實體，倉儲就自定義添加，不過一定要遵循命名規范。

下一節我們轉到Web Api層，來實現倉儲的依賴注入

源碼地址： https://github.com/wangyulong0505/Dinner