On 16-5-2019 18:40, Mark Rotteveel mark@... [Firebird-Java]
wrote:

> On 2019-05-16 16:22, sbailey@... [Firebird-Java]
> wrote:
>> My java says that it is Oracle Version 8 Update 201 (build
>> 1.8.0_201-b09).
>
> Ok, that version should support SHA-256 (unless it's explicitly disabled
> using a custom configuration).
>
>> The Jaybird version looks like 11-4.0.0-beta-1.
>
> The 11 is not part of the version, it is part of the classifier that
> identifies the target Java version (Java 11 in this case), but that
> version cannot run on Java 8, which might indicate that your tool is
> using its own JVM.

Based on my testing, if you used "Automatic Download Driver from
Repository" (which will download Jaybird 3.0.4 as well) before using
"Upload Driver File" to upload jaybird-full-java11-4.0.0-beta-1, then
even if you explicitly select it to use 4.0.0-beta-1, it will use the
downloaded version of Jaybird 3.0.4.

This can be checked by executing the following from within DbSchema:

select MON$CLIENT_VERSION, MON$AUTH_METHOD
from MON$ATTACHMENTS r
where MON$ATTACHMENT_ID = CURRENT_CONNECTION

This will report Jaybird 3.0.4-JDK_1.8 for the MON$CLIENT_VERSION

This has probably to do with how DbSchema manages its classpath and
loading order. By removing jaybird-full-3.0.4.jar from
C:\Users\<username>\.DbSchema\drivers\Firebird and keeping
jaybird-full-java11-4.0.0-beta-1.jar in that folder you should be able
to switch to using Jaybird 4. You can verify it with above query.

Mark
--
Mark Rotteveel