No need to create garbage if settings have value

on table containing more than one LOB column

found by CI and the new meta locking debugging stuff

after my previous commit which removed the use of the system session. Since we are taking the meta lock here, we don't need any extra synchronization

so we catch more output if stuff goes wrong

I can't see why this would be necessary - it's a DDL command, so we're going to call commit() immediately regardless

since  we moved the auto-analyze calls to only happen at commit time

as a consequence of my previous change to create views on the current session instead of the system session

instead of system session. This appears to have been introduced in

   commit ce7fd11d
   Author: Thomas Mueller <thomasmueller@users.noreply.github.com>
   Date:   Thu Jun 28 04:33:33 2007 +0000

but does not seem to be necessary anymore.

found by setting breakpoint for NPE. And pass in the socket to Transfer in the constructor, since all of the usage sites need to immediately set it.

Logo

Updates to MathUtils

the expected range. Also handle the exception at all call sites.

This is an O(1) implementation compared to the previous O(log n).
In my tests it was faster for all values >4 (int) / >8 (long).