The problem is twofold:
First Firebird 3 uses tighter security and has the old authentication mechanism disabled by default. So clients depending on older connection libraries will not work out of the box.
To allow the old authentication mechanism to work, the following setting needs to be set in firebird.conf:
AuthServer = Legacy_Auth, Srp, Win_Sspi
(be sure to remove the #
prefix)
Second, the pure-java wire protocol implementation of Jaybird (the Firebird JDBC driver) uses an outdated authentication mechanism that is not supported by this Legacy_Auth
option. Using Jaybird to connect to Firebird 3 at this time will only work if you use the native option (with the jdbc:firebirdsql:native:
URL-prefix and jaybird2x.dll and fbclient.dll).
Addendum 1
Firebird 3 (since Alpha 1) has now also implemented the old authentication method used by Jaybird, so Jaybird will now also work without using the native library (as long as the legacy authentication is enabled, and the user has been setup with the legacy usermanager).
See also Jaybird and Firebird 3
Addendum 2
Jaybird 3 and higher support the more secure Srp authentication model out of the box, and Jaybird 3.0.4 introduced support for the wire protocol encryption. This means that it can connect to Firebird 3 without additional configuration.
The syntax you're looking for is here
CREATE {DATABASE | SCHEMA} ... [PAGE_SIZE [=] size] ...
[DEFAULT CHARACTER SET charset [COLLATION collation]] ...
[DIFFERENCE FILE 'filepath']
size ::= 4096 | 8192 | 16384
Also check out this page and this link from it specifically
about case insensitive searches and collations on columns.
The good news is that you can set it both by database and column.
Also, check this out - you can also use "shadow" columns if you
can't get exactly what you want "out of the box" - i.e. UPPER()
function.
Best Answer