2016-02-01 17:42 GMT+01:00 Ben Hood <[email protected]>: > On Thu, Jan 28, 2016 at 5:07 PM, Lukas Eder <[email protected]> wrote: > > 2016-01-26 19:49 GMT+01:00 Ben Hood <[email protected]>: > > Same here. :) The weirdest bug I've ever encountered was a single missing > > bank account transaction for only a single customer in only a single > > E-Document, and only on October 31, 2010. Turns out that transactions > were > > searched using the following predicate (pseudo code): > > > > TRANSACTION_DATE BETWEEN TRUNC(beginning of month) AND TRUNC(end of > > month + 24 * 60 * 60 * 1000 milliseconds) > > > > Turns out that in Switzerland, 2010-10-31 had 25 hours (daylight savings > > time), and because it's a Sunday, no one noticed as there are hardly any > > bank account transactions on Sundays :) > > Do you think that Block Chain DBs can handle DST? And if so, when is > JOOQ going to bind to them? >
;-) > > You're right. The DefaultBinding inherited a bit of legacy. Its > procedural > > if-else blocks are also a performance issue. The method is too large to > be > > inlined by the JIT, plus after a couple of branches, if-else tends to be > > slower than dynamic dispatch (https://github.com/jOOQ/jOOQ/issues/4930). > > Interestingly enough, I was speaking to one of the Scala compiler guys > years ago who was telling me that polymorphic dispatch was implemented > quite efficiently in the JVM. > It is. But it can bite you as well (in hot loops): http://shipilev.net/blog/2015/black-magic-method-dispatch Although, not as bad as large if-else blocks. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
