Jaybird should specify dialect 3 in dpb when no explicit dialect was set. [JDBC327] #373
Comments
|
Commented by: @mrotteveel To be fixed in Jaybird 2.2.4. The new wire protocol implementation in 2.3 already fixed this. |
Modified by: @mrotteveeldescription: 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, as the dialect always needs to be passed when preparing statements. => 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, as the dialect always needs to be passed when preparing statements and there Jaybird defaults to dialect 3 if no dialect is specified. |
Modified by: @mrotteveeldescription: 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, as the dialect always needs to be passed when preparing statements and there Jaybird defaults to dialect 3 if no dialect is specified. => 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. |
|
Commented by: @mrotteveel Before attach/create a dpb item with dialect 3 is inserted if no dialect was set. |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
firebird-automations
added
affect-version: Jaybird 2.2.3
affect-version: Jaybird 2.2.2
affect-version: Jaybird 2.2.1
affect-version: Jaybird 2.2
affect-version: Jaybird 2.1.6
fix-version: Jaybird 2.2.4
fix-version: Jaybird 3.0.0
resolution: fixed
priority: major
component: jdbc driver
type: bug
labels
Submitted by: @mrotteveel
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.
Commits: b387598 FirebirdSQL/fbt-repository@778fa96
The text was updated successfully, but these errors were encountered: