You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
description: 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.
description: 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.
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: