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
Support for Firebird 3.0 [DNET630] #590
Comments
Commented by: @cincuranet What changed data structures you're talking about? |
Commented by: Mark Junker (fubar-coder) Here's a stack trace when I try to open an already opened database: System.IndexOutOfRangeException: Der Index war außerhalb des Arraybereichs. |
Commented by: @cincuranet Are you using latest provider? Does this happen only on FB3 and FB2.5.x is OK? This doesn't look like FB3 caused to me. |
Commented by: Mark Junker (fubar-coder) Yes, I'm using 4.8.0.0 and this happens with FB3 only. When using the FB2.5 DLLs, I get the following exception: FirebirdSql.Data.FirebirdClient.FbException (0x80004005): I/O error during "CreateFile (open)" operation for file "D:\DATALINE\DATALINE.OFFICE.MFC\BUILD\DEBUG\DATA\MUSTER.FDB" It might be an interesting for you, that the other application opens the database using a Firebird server, while my test application tries to open the DB directly (embedded). |
Modified by: @cincuranet |
Modified by: @cincuranetstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @cincuranet |
Modified by: @cincuranet |
Modified by: @cincuranetComponent: Entity Framework [ 10110 ] Component: Entity Framework Core [ 10160 ] |
Modified by: @cincuranetVersion: 4.8.1.0 [ 10720 ] => |
Commented by: @dyemanov I've found possible incompatibility with FB3. The native fbclient v3 always passes isc_dpb_utf8_filename (even if it wasn't specified by user) and all DPB strings are encoded in UTF8. Provider passes everything "as is" (using system encoding), similar to how FB 2.5 fbclient works. This may break monitoring if isc_dpb_process_name contains non-ASCII characters and server's locale is different from the client's one (example: CP1251 on the Windows client, UTF8 on the Linux server). It would be convinient to follow the fbclient logic -- i.e. always pass isc_dpb_utf8_filename (and transliterate all DPB strings accordingy) -- for protocol P13 and above. |
Commented by: @cincuranet OK. Will do. Thanks Dmitry. |
Closing in favor of separate issues. |
AFAIS, the issue I described earlier still exists. It makes monitoring usage impossible for many clients using .NET provider. Jiri, could you please post an update, when we may expect it to be fixed/improved? |
@dyemanov Can you create separate issue for that? |
Done, see #1020. |
Thanks. |
Submitted by: Mark Junker (fubar-coder)
Jira_subtask_outward DNET631
Jira_subtask_outward DNET642
Jira_subtask_outward DNET644
Jira_subtask_outward DNET645
Jira_subtask_outward DNET647
Jira_subtask_outward DNET649
Jira_subtask_outward DNET650
Jira_subtask_outward DNET652
Jira_subtask_outward DNET653
Jira_subtask_outward DNET672
Jira_subtask_outward DNET675
Jira_subtask_outward DNET676
Jira_subtask_outward DNET706
Jira_subtask_outward DNET760
Jira_subtask_outward DNET773
Jira_subtask_outward DNET784
Relate to DNET836
Votes: 4
It seems that the Firebird http://ADO.NET driver doesn't support Firebird 3.0 beta 2 yet. At least two things come to mind that probably have to be changed:
* Support for BOOLEAN data type
* Support for changed data structures
* I found at least one situation where the data structure was changed: When I try to open an already opened embedded database
The text was updated successfully, but these errors were encountered: