Subject Re: SQLWarning for Dialect
Author Roman Rokytskyy
Hi,

> That's when I see it, the first time a connection is reused after
> being created. We are using Firebird as our server which I am
> guessing only supports dialect level 1. It turns out to be
> innocuous but not intermittent.

Firebird server supports all dialects. That's the problem with your
database. You can fix it with gfix or some GUI tool (IB Console,
QuickDesk, etc.). Also you can fix this with Jaybird driver by adding
following property to JDBC connection properties:

Properties info = new Properties();
info.setProperty("user", "sysdba");
info.setProperty("password", "masterkey");
info.setProperty("set_db_sql_dialect", "3");

Connection con = DriverManager.getConnection(url, info);

Or you can add this property to JDBC URL:

jdbc:firebirdsql:...my.gdb?set_db_sql_dialect=3

Note, this does not work in InterClient.

> Should I do anything to prevent this from happening?

It's up to you. Dialect 1 is deprecated but working in Firebird 1.0.
Dialect 3 will be the only dialect in future major versions of
Firebird.

> Fwiw, we are planning to move to Jaybird as soon as we get some
> breathing time and will definitely try to contribute to the team.

Great! Looking forward to see you here.

Best regards,
Roman Rokytskyy