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
Historically, BLOB IDs were described as blr_quad in remote messages, because older server versions don't understand blr_blob2. v3 fbclient breaks this compatibility by sending blr_blob2 over the wire. ISQL connects fine, SHOW VERSION executes fine, but "select * from rdb$database" throws "error reading data from the connection".
I suppose we could simply revert back to the old behavior, but a more clever approach would be to check the protocol version and use blr_blob2 only if the server is known to understand it. I'm preparing the patch at the moment.
Submitted by: @dyemanov
Historically, BLOB IDs were described as blr_quad in remote messages, because older server versions don't understand blr_blob2. v3 fbclient breaks this compatibility by sending blr_blob2 over the wire. ISQL connects fine, SHOW VERSION executes fine, but "select * from rdb$database" throws "error reading data from the connection".
I suppose we could simply revert back to the old behavior, but a more clever approach would be to check the protocol version and use blr_blob2 only if the server is known to understand it. I'm preparing the patch at the moment.
Commits: 1776ee0 FirebirdSQL/fbt-repository@cda2aec
The text was updated successfully, but these errors were encountered: