Issue Details (XML | Word | Printable)

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

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

Jaybird should specify dialect 3 in dpb when no explicit dialect was set.

Created: 26/Oct/13 01:02 PM   Updated: 08/Dec/13 09:47 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.1.6, Jaybird 2.2, Jaybird 2.2.1, Jaybird 2.2.2, Jaybird 2.2.3
Fix Version/s: Jaybird 2.2.4, Jaybird 3.0

Time Tracking:
Not Specified


 Description  « Hide
When no explicit dialect is specified in the connection string or connection properties, then no dialect is sent in the DPB, this turns out to be wrong, because Firebird will default to dialect 1.

The impact of this is not very high: the only known effect is that (case sensitive) quoted rolenames do not work. Dialect 3 queries work as the dialect always needs to be passed when preparing statements and there Jaybird defaults to dialect 3 if no dialect is specified.

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 26/Oct/13 01:03 PM
To be fixed in Jaybird 2.2.4. The new wire protocol implementation in 2.3 already fixed this.

Mark Rotteveel added a comment - 26/Oct/13 04:14 PM
Before attach/create a dpb item with dialect 3 is inserted if no dialect was set.