Well, I built from GIT (commit 78155dab9d5242bc599e695e11f9f5566872b3be,
from 2019-01-05 by Noel Grandin) and the performance falloff is either no
longer there, or has been pushed out far enough that it appears to no
longer be an issue.
Can't wait for 1.4.198 to be released!! Any idea what the
Thanks! That certainly helps!
I tried MULTI_THREADED today with 1.4.197 and found some odd behavior with
regards to the application I'm testing with. Some foreign key errors
because inserts were being processed (apparently) out-of-order, which based
on how the application is coded, should be
On Friday, December 21, 2018 at 2:31:19 AM UTC-6, Evgenij Ryazanov wrote:
>
> In 1.4.197 MULTI_THREADED is not set by default. You may enable it for
> MVStore, but be careful, there were issues in some specific use cases.
> In upcoming 1.4.198 this setting is true by default for MVStore engine
>
As per the JavaDoc, Connection.createArray() should raise
a SQLFeatureNotSupportedException if the feature is not supported, and a
SQLException for other errors such as if a database error occurs, the JDBC
type is not appropriate for the typeName and the conversion is not
supported, the
