ASP.NET Zero with Firebird -- exceptions on commit #4541

aprsystem created 6 years ago

Hello.

We are trying to make ASP.NET Zero work with Firebird 3.0. We found a workaround for unsupported byte/tinyint mapping in Firebird, then we managed to add initial migration and successfully created database schema.

But now we're facing another issue -- when we launch the .Host project, the Firebird provider throws an InvalidOperationException, because apparently ABP is trying to commit a completed transaction ("This transaction has completed and it is no longer usable.").

We have a solution which demonstrates the issue, including the source projects for the EFCore.Firebird and FirebirdSql.Data.FirebirdClient libraries. The only deviation from upstream Firebird libraries is the aforementioned two-line workaround for byte mapping in EFCore.Firebird. When running the code, please use the .Web solution, because the .All one may have some references broken. The initial migration is already present. We also included the generated database (CORETESTDB.FDB). The Firebird 3 server is obviously required, with the WireCrypt feature disabled in server config file. The default db file location is C: root directory, as seen in the connection strings.

As we said, after the database is set up, launching the .Host project results in exception and the Swagger UI fails to load. However, the Abp tables are correctly populated on first launch with default data (AbpLanguages, AbpUsers, etc.).

When we tried catching the exception in FbTransaction.Commit() method (it is thrown by the guard method EnsureCompleted()) and then returning from the catch block, then we were able to reach the Swagger UI. Those exceptions seem to be very frequent. Then we got some other (likely unrelated) issues with SQL parameters generation when trying to log in as Admin with the Angular frontend, but that's another story.

For now, we would like to know if there is anything we can do to avoid the commit exceptions.

5 Answer(s)