René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Specification hash breaking change for sql IN operator","articleBody":"I upgraded the SharpRepository packages of a solution from version 1.5.0.2 to version 2.0.4.3, and I noticed that the generated cache key is different between the two releases when the sql \"IN\" operator is used.\r\nFor example, a typical query like the following:\r\n\r\n```csharp\r\nvar collection1 = new List\u003cint\u003e() { 1, 2, 3 };\r\nvar collection2 = new List\u003cint\u003e() { 4, 5, 6 };\r\n\r\nvar results1 = repo.FindAll(x =\u003e collection1.Contains(x.Id));\r\nvar results2 = repo.FindAll(x =\u003e collection2.Contains(x.Id));\r\n```\r\n\r\nshould produce two different cache keys because the collection values are different, instead version 2.0.4.3 produces the same value.\r\n\r\nSo I checked the unit test code and found that a **\"Different_Predicate_With_Variable_Array_Will_Give_Different_Hash\"** unit test exists, but in the v1.5.0.2 it correctly checks that \r\n```csharp\r\nhash1.ShouldNotEqual(hash2).\r\n```\r\nInstead the newer 2.0.2 version checks \r\n```csharp\r\nhash1.ShouldBe(hash2) \r\n```\r\nthat is obviously wrong.\r\n\r\nIs this an intentional breaking change or just a bug?\r\n","author":{"url":"https://github.com/Liu79","@type":"Person","name":"Liu79"},"datePublished":"2018-09-04T15:25:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/223/SharpRepository/issues/223"}