Fix Version: Jaybird 2.2.15 [ 10860 ]

Fix Version: Jaybird 3.0.5 [ 10873 ]

Fix Version: Jaybird 4 [ 10441 ]

description: The version number parsing done on the value returned by isc_info_firebird_version is wrong. The implementation assumes the returned value is a single string, but apparently it is a compound binary response that consists of multiple length prefixed segments. This causes issues with parsing, like - for example - JDBC152 and others.

As it turns out, historically what we thought was a separator in the version string (either ",", "-" or "/"), was actually a length by in the string that on our systems just happened to look like a separator because our hostnames had length 6 which made the extended version string either 44(,), 45(-) or 47(/) bytes.

=>

The version number parsing done on the value returned by isc_info_firebird_version is wrong. The implementation assumes the returned value is a single string, but apparently it is a compound binary response that consists of multiple length prefixed segments. This causes issues with parsing, like - for example - JDBC152 and others.

As it turns out, historically what we thought was a separator in the version string (either ",", "-" or "/"), was actually a length byte in the string that on our systems just happened to look like a separator because our hostnames had length 6 which made the extended version string either 44(,), 45(-) or 47(/) bytes.

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

status: Resolved [ 5 ] => Closed [ 6 ]