New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulty returning the product version with the legacy connection #7819
Comments
The DBX driver call The Firebird answer is The guess is that driver can't correctly handle We can make version string shorter or truncate it according to the client buffer size but I not sure we should do it. |
We never did that in prior versions and nobody complained so far, while we supposedly have some DBX users. Weird ;-) |
I guess DBX have not much users and not all of them tested our RC versions ;) |
From another POV - DBX users are unable to test RC, which also not good. |
The simplest is change 'Release Candidate' => 'RC' . |
In RC2 |
They are able to test DBX and found an obvious bug in it. Now the ball is on Embarcadero side (or whoever is the author of the driver). |
The problem is that DBXExpress is a discontinued drive. That's why I said it's a legacy application. |
It means that you must fix the application, that's all. Not a Firebird issue. |
As it is a legacy application, it is not possible to change everything at once, this is already being modified gradually by the team. But as there is a legacy configuration in Firebird, I understand that it could work, as it worked in the beta version. But that's just my point of view. |
Marcelo, your application is unable to handle version information string that is a bit longer than one in beta version - yep, strlen("release candidate") > strlen("beta"). :-) Pay attention that length of version string in LEGACY API is limited somewhere around 255 bytes (a bit smaller - but one returned to your app is definitely MUCH shorter). I.e. your application violates legacy rules. That's why it does not work. |
@AlexPeshkoff, it is not an applicaiton bug, it is DBX driver problem. The first question is should we change something on our side or recommend @MarceloZaniboni to wait for final release of Firebird 5 ? |
On 11/1/23 16:24, Vlad Khorsun wrote:
@AlexPeshkoff <https://github.com/AlexPeshkoff>, it is not an
applicaiton bug, it is DBX driver problem.
AFAIU, DBX is closed source and can't be fixed easily.
I understand it - but as long as app was built using DBX it becomes app
problem.
The first question is should we change something on our side or
recommend @MarceloZaniboni <https://github.com/MarceloZaniboni> to
wait for final release of Firebird 5 ?
As I've already replied - the simplest solution is to call 'release
candidate 2' RC2. Overflow will be avoided - and this should not harm
others.
|
Perhaps, they should try DBX driver by Devart: https://www.devart.com/dbx/interbase/ |
Ok, if there will be no objections, I'll commit it tomorrow. |
It also fixed #7819 : Difficulty returning the product version with the legacy connection
Check next snapshot build, please |
Thank you very much, resolved! |
I am having difficulties with the Firebird 5.0 Release Candidate 1 version. The same did not happen in the Firebird 5.0 Beta 1 version, regarding version changes in legacy applications developed in Delphi Tokyo using the DBExpress (TSQLConnection) component.
Test with the latest snapshot version available, the problem still persists.
Next, send a test application for analysis if possible.
And two images, one with the problem in the latest version of Release Candidate 1 available and another with the result of beta version 1.
Thank you very much in advance.
Thanks,
Marcelo Zaniboni
TestLegancyCnxFB50.zip
The text was updated successfully, but these errors were encountered: