Path: csiph.com!news.redatomik.org!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Which databases are the most used with Java Date: Thu, 17 Aug 2017 18:14:14 -0400 Organization: Aioe.org NNTP Server Lines: 19 Message-ID: References: <87y3qovwjb.fsf@munus.decebal.nl> <87tw1bx2c9.fsf@munus.decebal.nl> <87a833wzcx.fsf@munus.decebal.nl> <87pobz9yv5.fsf@munus.decebal.nl> <87h8x9pfi8.fsf@munus.decebal.nl> <87inhpni1f.fsf@munus.decebal.nl> NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:37264 On 8/17/2017 5:52 PM, lewbloch@gmail.com wrote: > So when a query is hardcoded you prefer to give up the efficiency of `PreparedStatement`? The *potential* efficiency. JDBC standard does not guarantee any extra efficiency by using PreparedStatement over plain Statement. Some databases may cache execution plans for PreparedStatement but not for over plain Statement. Other does not make a difference. It is my impression that most databases today cache execution plans even for plain Statement. Arne