Path: csiph.com!au2pb.net!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Cecil Westerhof Newsgroups: comp.lang.java.programmer Subject: Re: Performance JPA Date: Fri, 20 Nov 2015 09:13:38 +0100 Organization: Decebal Computing Lines: 27 Message-ID: <87twohytot.fsf@Equus.decebal.nl> References: <87lhagkcsh.fsf@Equus.decebal.nl> <563763d9$0$23727$e4fe514c@news.xs4all.nl> <87d1vrk20x.fsf@Equus.decebal.nl> <56389a9e$0$23778$e4fe514c@news.xs4all.nl> <5639ce9d$0$23755$e4fe514c@news.xs4all.nl> <87611ihxee.fsf@Equus.decebal.nl> <5639ef43$0$23781$e4fe514c@news.xs4all.nl> <56406add$0$23854$e4fe514c@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="528adfd6ad074c92fdc6a7f8fb9e23d8"; logging-data="10391"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19mCFMhzcb9mdg+cBg1Xb7o6FCFiYdvPCU=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:RCsQapvBLxUcD3g/dNl1I9o4Hu0= sha1:h/CjRuaOZcUkfCTvmLdsFDxxDI0= X-Homepage: http://www.decebal.nl/ Xref: csiph.com comp.lang.java.programmer:33147 On Monday 9 Nov 2015 10:43 CET, silvio@internet.com wrote: > On 11/08/2015 04:18 AM, Arne Vajhøj wrote: >> >> You can code that right and wrong using JDBC - and you can code >> that right and wrong using ORM. >> > > Yes, but if you do it the wrong way using JDBC you have to code it > in the least obvious way. That just demonstrates a lack of knowledge > about how to work with an RDBMS in general and is not caused (or can > be fixed) by JDBC. > > The ORM code that caused this particular behavior looked very clean > and neat to a whole team of programmers that had gone over it dozens > of times to see if they could explain the poor performance. The > problem was that they did not have enough knowledge about RDBMSs AND > data abstraction layer inner workings to fully grasp what was going > on behind the scenes. Is it possible to share what was happening? It had nothing to do with my case, but I always like to learn. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof