dapper

I can't seem to find documentation or examples for my problem (been searching a while now). I think my problem is pretty straightforward, so here goes. I have two tables. My primary table is called Persons and the secondary table is PersonEntries. For each person in Person table, i can have 0 or more entries in the PersonEntries table. Like this. Table: Person Id Name Table: PersonEntry PersonId CheckinTime CheckoutTime I have two objects like this public class Person { public string Name; public List<PersonEntry> PersonEntries; } public class PersonEntry { public DateTime CheckinTime; public

Using dapper , how can I insert a C# List to database. Previously without dapper I used the below code to insert the List values to database . try { connection.Open(); for (int i = 0; i < processList.Count; i++) { string processQuery = "INSERT INTO PROCESS_LOGS VALUES (@Id, @st_Time, @ed_Time, @td_Time)"; command = new SqlCommand(processQuery, connection); command.Parameters.Add("Id", SqlDbType.Int).Value = processList[i].ID; command.Parameters.Add("st_Time", SqlDbType.DateTime).Value = processList[i].ST_TIME; command.Parameters.Add("ed_Time", SqlDbType.DateTime).Value = processList[i].ED_TIME

I use dapper to return objects from my database as IEnumerable. As default dapper has buffer setting set to true. How does this work? If dapper cache the first query and then get the objects from memory. What happens if someone edit/delete/add rows in the table. Must dapper recache all data again for this query? The buffer is unrelated to cache. Dapper does not include any kind of data-cache (although it does have a cache related to how it processes commands, i.e. "this command string, with this type of parameter, and this type of entity - has these associated dynamically generated methods to

I have a dictionary of values Eg "Name": "Alex" Is there a way to pass this to Dapper as arguments for a query? Here is an example showing what I want to do. IDictionary<string, string> args = GetArgsFromSomewhere(); string query = "select * from people where Name = @Name"; var stuff = connection.Query<ExtractionRecord>(query, args); Yes: var dbArgs = new DynamicParameters(); foreach(var pair in args) dbArgs.Add(pair.Key, pair.Value); Then pass dbArgs in place of args : var stuff = connection.Query<ExtractionRecord>(query, dbArgs); Alternatively, you can write your own class that implements

I've been playing with Dapper, but I'm not sure of the best way to handle the database connection. Most examples show the connection object being created in the example class, or even in each method. But it feels wrong to me to reference a connection string in every clss, even if it's pulling from the web.config. My experience has been with using a DbDataContext or DbContext with Linq to SQL or Entity Framework, so this is new to me. How do I structure my web apps when using Dapper as my Data Access strategy? I created extension methods with a property that retrieves the connection string from

背景 随着公司业务的高速发展，公司服务之间的调用关系愈加复杂，如何理清并跟踪它们之间的调用关系就显的比较关键。线上每一个请求会经过多个业务系统，并产生对各种缓存或者 DB 的访问，但是这些分散的数据对于问题排查，或者流程优化提供的帮助有限。在这样复杂的业务场景下，业务流会经过很多个微服务的处理和传递，我们难免会遇到这些问题: 一次请求的流量从哪个服务而来？ 最终落到了哪个服务中去？ 为什么这个请求这么慢? 到底哪个环节出了问题? 这个操作需要依赖哪些东西? 是数据库还是消息队列? Redis挂了，哪些业务受影响? 设计目标 低消耗性：跟踪系统对业务系统的影响应该做到足够小。在一些高度优化过的服务，即使一点点损耗也容易察觉到，而且有可能迫使在线负责的部署团队不得不将跟踪系统关停 低侵入性：作为非业务组件，应当尽可能少侵入或者无侵入业务系统，对于使用方透明，减少开发人员的负担 时效性：从数据的收集产生，到数据计算处理，再到最终展现，都要求尽可能快 决策支持：这些数据是否能在决策支持层面发挥作用，特别是从 DevOps 的角度 数据可视化：做到不用看日志通过可视化进行筛选 实现功能 故障定位：调用链路跟踪，一次请求的逻辑轨迹可以完整清晰的展示出来。 性能分析：调用链的各个环节分别添加调用耗时，可以分析出系统的性能瓶颈，并针对性的优化。 数据分析：调用链是一条完整的业务日志

How does Dapper help protect against SQL injections? I am testing out different DAL technologies and have to choose one to be secure our site. I'm leaning towards Dapper (http://code.google.com/p/dapper-dot-net/), but need some help learning about security. How does Dapper help protect against SQL injections? It makes it really, really easy to do fully parameterized data access, without ever needing to either concatenate input. In particular, because you don't need to jump through lots of "add parameter, set the parameter type, check for null because ADO.NET has sucky null-handling , rinse