Ralf,
> Tried the snapshot and can't reproduce the problem currently. I presumably
> misinterpreted the tracker info's.
According to:
https://github.com/FirebirdSQL/firebird/commits/B3_0_Release
The fix has been committed on July 13, so the current Windows snapshot
from July 29 should include
Tried the snapshot and can't reproduce the problem currently. I presumably
misinterpreted the tracker info's.
-Ursprüngliche Nachricht-
Von: Ralf Jansen [mailto:ralf.jan...@mailstore.com]
Gesendet: Donnerstag, 4. August 2016 14:55
An: For users and developers of the Firebird .NET provid
Thanks Thomas,
>From where to get that? The snapshot build on firebirdsql.org is older than
>the tracker case. So the fix is presumably not in there.
I could get the master from Github but the recent commit history doesn't look
like CORE-5307 has been fixed (at least it's not stated directly).
On 04.08.2016 14:13, Thomas Steinmaurer wrote:
> Ralf,
>
>> I recently switched from an older provider version (2.x something) to
>> the current 5.0.5.0 build and use it in an embedded scenario.
>>
>> In that process I also switched from FB 2.5 to 3.0
>>
>>
>>
>> I have stability problems when the
Ralf,
> I recently switched from an older provider version (2.x something) to
> the current 5.0.5.0 build and use it in an embedded scenario.
>
> In that process I also switched from FB 2.5 to 3.0
>
>
>
> I have stability problems when the system gets under heavy load with
> concurrent transactio
I recently switched from an older provider version (2.x something) to the
current 5.0.5.0 build and use it in an embedded scenario.
In that process I also switched from FB 2.5 to 3.0
I have stability problems when the system gets under heavy load with concurrent
transactions/connections.
I rece