https://kaveland.no/tags/jdbc/Recent content in Jdbc on Robin's blogHugo -- 0.145.0en-usSat, 21 Sep 2024 00:00:00 +0000https://kaveland.no/posts/2024-09-21-equals-any-over-where-in/Sat, 21 Sep 2024 00:00:00 +0000https://kaveland.no/posts/2024-09-21-equals-any-over-where-in/<p>In my post about <a href="https://kaveland.no/posts/2024-08-30-multi-selecting-by-composite-key/">batch operations</a>, I used the <code>where id = any(:ids)</code> pattern, with <code>ids</code> bound to a JDBC array. I&rsquo;ve gotten questions about that afterwards, asking why I do it like that, instead of using <code>in (:id1, :id2, ...)</code>. Many libraries can take care of the dynamic SQL generation for you, so often you can just write <code>in (:ids)</code>, just like the array example. I would still prefer to use the <code>= any(:ids)</code> pattern, and I decided to write down my reasoning here.</p>https://kaveland.no/posts/2024-08-30-multi-selecting-by-composite-key/Fri, 30 Aug 2024 00:00:00 +0000https://kaveland.no/posts/2024-08-30-multi-selecting-by-composite-key/<p>Throughout a career as a software developer, you encounter many patterns. Some appear just often enough to remember that they exist, but you still need to look them up every time. I&rsquo;ve discovered that writing things down helps me remember them more easily. This particular pattern is very useful for my current project. So, it&rsquo;s time to write it down and hopefully commit it to memory properly this time. Although this post is specific to PostgreSQL, I&rsquo;m sure other databases have the necessary features to achieve the same results efficiently.</p>