On Monday, February 20, 2017 5:20:06 PM EST you wrote:

> Just so it is not buried in the other thread, easy for others to find. It

> seems for anyone coming from Jaybird 2.x to Jaybird 3.x. The settings that

> must be in place for Jaybird 3.x, also work for 2.x. Which makes it a good

> migration path setting. Add now to Jaybird 2.x, and your good for Jaybird

> 3.x

>

> For direct JDBC connection, not in a container, etc add both

> lc_type and chartSet.

>

> jdbc:firebirdsql:my.domain.com/3050:/path/to/data.fdb?

> lc_type=NONE&charSet=ISO-8895-1

 

Seeing a bit of inconsistency. For some this works, for others not. I cannot explain why it works for some and not others. Database are the same charset.

jdbc:firebirdsql:my.domain.com/3050:/path/to/data.fdb?lc_type=NONE

 

This seems to be more reliable. I have not had any problems connecting.

jdbc:firebirdsql:my.domain.com/3050:/path/to/data.fdb?charSet=ISO-8895-1

 

Both do not seem to be required, but do not seem to hurt if both are set. Just seems charSet is more reliable than lc_type. I think the lc_type allows Jaybird 3 to work with Firebird < 3. When you have Jaybird 3.x and Firebird 3.x, you need to use charSet not lc_type.

 

--

William L. Thomson Jr.