From 3c7cde28b55ecaa590c2eb5430d4eff460ae388e Mon Sep 17 00:00:00 2001 From: Nick Craver Date: Sun, 20 May 2018 08:07:59 -0400 Subject: [PATCH] Fix #451 --- Readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index 5f20dd70d..efbaf7137 100644 --- a/Readme.md +++ b/Readme.md @@ -360,7 +360,7 @@ using (var reader = connection.ExecuteReader("select * from Shapes")) Limitations and caveats --------------------- -Dapper caches information about every query it runs, this allow it to materialize objects quickly and process parameters quickly. The current implementation caches this information in a `ConcurrentDictionary` object. The objects it stores are never flushed. If you are generating SQL strings on the fly without using parameters it is possible you will hit memory issues. We may convert the dictionaries to an LRU Cache. +Dapper caches information about every query it runs, this allow it to materialize objects quickly and process parameters quickly. The current implementation caches this information in a `ConcurrentDictionary` object. Statements that are only used once are routinely flushed from this cache. Still, if you are generating SQL strings on the fly without using parameters it is possible you may hit memory issues. Dapper's simplicity means that many feature that ORMs ship with are stripped out. It worries about the 95% scenario, and gives you the tools you need most of the time. It doesn't attempt to solve every problem.