Issue Details (XML | Word | Printable)

Key: JDBC-535
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

Version number parsing in GDSServerVersion and AbstractFbDatabase (and GDS for earlier versions) is incorrect

Created: 06/Jun/18 01:37 PM   Updated: 07/Sep/18 03:41 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.2.12, Jaybird 2.2.13, Jaybird 3.0.0, Jaybird 3.0.1, Jaybird 3.0.2, Jaybird 3.0.3, Jaybird 2.2.14, Jaybird 3.0.4
Fix Version/s: Jaybird 3.0.5, Jaybird 2.2.15, Jaybird 4

 Description  « Hide
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 - JDBC-152 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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 09/Jun/18 12:45 PM
Committed fix that will read the version in segments