You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(55) |
Dec
(36) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(38) |
Feb
(108) |
Mar
(79) |
Apr
(95) |
May
(64) |
Jun
(130) |
Jul
(146) |
Aug
(121) |
Sep
(96) |
Oct
(149) |
Nov
(161) |
Dec
(113) |
2004 |
Jan
(113) |
Feb
(163) |
Mar
(248) |
Apr
(132) |
May
(157) |
Jun
(160) |
Jul
(236) |
Aug
(284) |
Sep
(293) |
Oct
(277) |
Nov
(257) |
Dec
(356) |
2005 |
Jan
(203) |
Feb
(190) |
Mar
(220) |
Apr
(165) |
May
(124) |
Jun
(160) |
Jul
(190) |
Aug
(142) |
Sep
(152) |
Oct
(189) |
Nov
(187) |
Dec
(159) |
2006 |
Jan
(170) |
Feb
(151) |
Mar
(212) |
Apr
(262) |
May
(226) |
Jun
(196) |
Jul
(223) |
Aug
(165) |
Sep
(163) |
Oct
(348) |
Nov
(225) |
Dec
(141) |
2007 |
Jan
(261) |
Feb
(161) |
Mar
(222) |
Apr
(193) |
May
(121) |
Jun
(157) |
Jul
(151) |
Aug
(159) |
Sep
(61) |
Oct
(123) |
Nov
(172) |
Dec
(96) |
2008 |
Jan
(104) |
Feb
(138) |
Mar
(131) |
Apr
(131) |
May
(74) |
Jun
(107) |
Jul
(89) |
Aug
(89) |
Sep
(172) |
Oct
(158) |
Nov
(119) |
Dec
(86) |
2009 |
Jan
(52) |
Feb
(84) |
Mar
(78) |
Apr
(83) |
May
(54) |
Jun
(79) |
Jul
(60) |
Aug
(62) |
Sep
(50) |
Oct
(147) |
Nov
(50) |
Dec
(70) |
2010 |
Jan
(135) |
Feb
(113) |
Mar
(74) |
Apr
(93) |
May
(35) |
Jun
(71) |
Jul
(33) |
Aug
(110) |
Sep
(47) |
Oct
(18) |
Nov
(61) |
Dec
(34) |
2011 |
Jan
(46) |
Feb
(47) |
Mar
(25) |
Apr
(24) |
May
(21) |
Jun
(22) |
Jul
(20) |
Aug
(51) |
Sep
(31) |
Oct
(42) |
Nov
(22) |
Dec
(22) |
2012 |
Jan
(31) |
Feb
(19) |
Mar
(25) |
Apr
(55) |
May
(16) |
Jun
(28) |
Jul
(33) |
Aug
(25) |
Sep
(32) |
Oct
(25) |
Nov
(52) |
Dec
(35) |
2013 |
Jan
(43) |
Feb
(18) |
Mar
(36) |
Apr
(45) |
May
(22) |
Jun
(13) |
Jul
(31) |
Aug
(24) |
Sep
(19) |
Oct
(59) |
Nov
(47) |
Dec
(25) |
2014 |
Jan
(27) |
Feb
(15) |
Mar
(38) |
Apr
(10) |
May
(15) |
Jun
(36) |
Jul
(24) |
Aug
(28) |
Sep
(16) |
Oct
(6) |
Nov
(44) |
Dec
(40) |
2015 |
Jan
(52) |
Feb
(22) |
Mar
(13) |
Apr
(17) |
May
(22) |
Jun
(36) |
Jul
(18) |
Aug
(41) |
Sep
(71) |
Oct
(60) |
Nov
(49) |
Dec
(43) |
2016 |
Jan
(60) |
Feb
(13) |
Mar
(21) |
Apr
(28) |
May
(23) |
Jun
(39) |
Jul
(17) |
Aug
(37) |
Sep
(33) |
Oct
(15) |
Nov
(22) |
Dec
(20) |
2017 |
Jan
(27) |
Feb
(40) |
Mar
(48) |
Apr
(19) |
May
(29) |
Jun
(2) |
Jul
(19) |
Aug
(36) |
Sep
(18) |
Oct
(10) |
Nov
(11) |
Dec
(5) |
2018 |
Jan
(5) |
Feb
(4) |
Mar
(5) |
Apr
(3) |
May
(4) |
Jun
(17) |
Jul
(7) |
Aug
(7) |
Sep
(12) |
Oct
(8) |
Nov
(2) |
Dec
|
2019 |
Jan
(8) |
Feb
(5) |
Mar
(3) |
Apr
(5) |
May
(3) |
Jun
(2) |
Jul
(8) |
Aug
(7) |
Sep
(3) |
Oct
(12) |
Nov
(7) |
Dec
(1) |
2020 |
Jan
(8) |
Feb
(3) |
Mar
(7) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
(25) |
Sep
(5) |
Oct
(3) |
Nov
(7) |
Dec
(16) |
2021 |
Jan
(11) |
Feb
(10) |
Mar
(16) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jiří Č. <ji...@ci...> - 2015-09-21 13:25:09
|
Hi, I just brought the branch up to date. Please hold your PRs for a week or so. I'll clean it up and do some final changes. Then we'll finish it, merge it and it'll go out (likely even before EF 6.2.0). -- Mgr. Jiří Činčura Independent IT Specialist |
From: Jiří Č. <ji...@ci...> - 2015-09-21 11:52:15
|
Here's the 4.8.0.0 tag building just fine https://ci.appveyor.com/project/cincura_net/firebirdsql-data-firebirdclient/build/0.0.0.452 . Without an error your have it's anybody's guess. -- Mgr. Jiří Činčura Independent IT Specialist On Mon, Sep 21, 2015, at 13:44, Nicolas F. Timmers wrote: > Hello, > > > > I'm getting na error when compiling the new version of .net provider 4_8 > on > the file "FbTransactionOption.cs" > > > > I Downloaded him from > http://sourceforge.net/projects/firebird/files/firebird-net-provider/4.8.0/ > > > > Any help ? > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Nicolas F. T. <nft...@ho...> - 2015-09-21 11:44:52
|
Hello, I'm getting na error when compiling the new version of .net provider 4_8 on the file "FbTransactionOption.cs" I Downloaded him from http://sourceforge.net/projects/firebird/files/firebird-net-provider/4.8.0/ Any help ? |
From: Геннадий З. <zab...@gm...> - 2015-09-20 14:53:45
|
> I don't think there is even an issue here After taking another view at what happens, I don't think either. The exception is thrown when similar updates are made for one field, from several threads, when NO_WAIT specified. Only this flag causes it to throw. No matter if you specify flags consistent or concurrency. As I understood this is expected behavior. NO_WAIT flag is set for any IsolationLevel specified for a FbTransaction. The behavior of such updates is different from MSSQL provider (it waits) and discovering this was a kind frustrating and resulted in this thread. On 20 September 2015 at 16:30, Alexander Muylaert-Gelein <amu...@ho...> wrote: > I don't think there is even an issue here. inside two different > transactions, you simply cannot update the same record. Who would win in > the end and what would be the end result. I'm pretty sure if you can solve > this, the firebird team would gladly implement this. > > a > > >> Date: Sun, 20 Sep 2015 14:12:25 +0300 >> From: zab...@gm... >> To: fir...@li... > >> Subject: Re: [Firebird-net-provider] Multithread insert >> >> I don't think that the issue in the .NET provider. It just forwards >> options to fbembed.dll for transactions it just TPB. And do it right. >> The problem is in the engine, I've retested it with C API and the >> behavior is similar to observed. My case is similar to the described >> here: http://www.firebirdfaq.org/faq109/. With just one difference: >> values field updated to is not depends on each other. I just update >> the same field from several threads. I've crutched this with skipping >> the exception because consistency is not a concern for this field. But >> IMO, there is an issue in the engine. >> >> On 20 September 2015 at 14:03, LtColRDSChauhan <rds...@gm...> wrote: >> >> Message: 3 >> >> Date: Thu, 17 Sep 2015 19:56:20 +0200 >> >> From: Ji?? ?in?ura <ji...@ci...> >> >> Subject: Re: [Firebird-net-provider] Multithread insert >> >> To: "For users and developers of the Firebird .NET providers" >> >> <fir...@li...> >> >> Message-ID: >> >> <144...@we...> >> >> Content-Type: text/plain; charset="UTF-8" >> >> >> >> On Thu, Sep 17, 2015, at 17:57, ???????? ?????? wrote: >> >> > Narrowed the problem. The cause is a multithreaded update of the same >> >> > record field. Transactions, as I said don't dispatch the issue. >> >> >> >> The advice is simple. Don't update same record (not only in .NET; >> >> anywhere, anytool). :D >> >> >> > Transactions issues in .NET Provider need to be addressed. >> > Multithread/parallel programming and transactions enable correct >> > exploitation of multicore machines. I understand Firebird 3.0 takes >> > major >> > advances in this area. >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Firebird-net-provider mailing list >> > Fir...@li... >> > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider >> > >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Firebird-net-provider mailing list >> Fir...@li... >> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > > ------------------------------------------------------------------------------ > > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > |
From: Alexander Muylaert-G. <amu...@ho...> - 2015-09-20 13:30:37
|
I don't think there is even an issue here. inside two different transactions, you simply cannot update the same record. Who would win in the end and what would be the end result. I'm pretty sure if you can solve this, the firebird team would gladly implement this. a > Date: Sun, 20 Sep 2015 14:12:25 +0300 > From: zab...@gm... > To: fir...@li... > Subject: Re: [Firebird-net-provider] Multithread insert > > I don't think that the issue in the .NET provider. It just forwards > options to fbembed.dll for transactions it just TPB. And do it right. > The problem is in the engine, I've retested it with C API and the > behavior is similar to observed. My case is similar to the described > here: http://www.firebirdfaq.org/faq109/. With just one difference: > values field updated to is not depends on each other. I just update > the same field from several threads. I've crutched this with skipping > the exception because consistency is not a concern for this field. But > IMO, there is an issue in the engine. > > On 20 September 2015 at 14:03, LtColRDSChauhan <rds...@gm...> wrote: > >> Message: 3 > >> Date: Thu, 17 Sep 2015 19:56:20 +0200 > >> From: Ji?? ?in?ura <ji...@ci...> > >> Subject: Re: [Firebird-net-provider] Multithread insert > >> To: "For users and developers of the Firebird .NET providers" > >> <fir...@li...> > >> Message-ID: > >> <144...@we...> > >> Content-Type: text/plain; charset="UTF-8" > >> > >> On Thu, Sep 17, 2015, at 17:57, ???????? ?????? wrote: > >> > Narrowed the problem. The cause is a multithreaded update of the same > >> > record field. Transactions, as I said don't dispatch the issue. > >> > >> The advice is simple. Don't update same record (not only in .NET; > >> anywhere, anytool). :D > >> > > Transactions issues in .NET Provider need to be addressed. > > Multithread/parallel programming and transactions enable correct > > exploitation of multicore machines. I understand Firebird 3.0 takes major > > advances in this area. > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Firebird-net-provider mailing list > > Fir...@li... > > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Геннадий З. <zab...@gm...> - 2015-09-20 11:12:32
|
I don't think that the issue in the .NET provider. It just forwards options to fbembed.dll for transactions it just TPB. And do it right. The problem is in the engine, I've retested it with C API and the behavior is similar to observed. My case is similar to the described here: http://www.firebirdfaq.org/faq109/. With just one difference: values field updated to is not depends on each other. I just update the same field from several threads. I've crutched this with skipping the exception because consistency is not a concern for this field. But IMO, there is an issue in the engine. On 20 September 2015 at 14:03, LtColRDSChauhan <rds...@gm...> wrote: >> Message: 3 >> Date: Thu, 17 Sep 2015 19:56:20 +0200 >> From: Ji?? ?in?ura <ji...@ci...> >> Subject: Re: [Firebird-net-provider] Multithread insert >> To: "For users and developers of the Firebird .NET providers" >> <fir...@li...> >> Message-ID: >> <144...@we...> >> Content-Type: text/plain; charset="UTF-8" >> >> On Thu, Sep 17, 2015, at 17:57, ???????? ?????? wrote: >> > Narrowed the problem. The cause is a multithreaded update of the same >> > record field. Transactions, as I said don't dispatch the issue. >> >> The advice is simple. Don't update same record (not only in .NET; >> anywhere, anytool). :D >> > Transactions issues in .NET Provider need to be addressed. > Multithread/parallel programming and transactions enable correct > exploitation of multicore machines. I understand Firebird 3.0 takes major > advances in this area. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > |
From: LtColRDSChauhan <rds...@gm...> - 2015-09-20 11:03:10
|
> > Message: 3 > Date: Thu, 17 Sep 2015 19:56:20 +0200 > From: Ji?? ?in?ura <ji...@ci...> > Subject: Re: [Firebird-net-provider] Multithread insert > To: "For users and developers of the Firebird .NET providers" > <fir...@li...> > Message-ID: > <144...@we...> > Content-Type: text/plain; charset="UTF-8" > > On Thu, Sep 17, 2015, at 17:57, ???????? ?????? wrote: > > Narrowed the problem. The cause is a multithreaded update of the same > > record field. Transactions, as I said don't dispatch the issue. > > The advice is simple. Don't update same record (not only in .NET; > anywhere, anytool). :D > > Transactions issues in .NET Provider need to be addressed. Multithread/parallel programming and transactions enable correct exploitation of multicore machines. I understand Firebird 3.0 takes major advances in this area. |
From: Mark R. <ma...@la...> - 2015-09-19 08:07:12
|
On 19-9-2015 07:00, Jiří Činčura wrote: > I have no idea. The website changes are done by another person, not me. > The site has been updated. Mark -- Mark Rotteveel |
From: Jiří Č. <ji...@ci...> - 2015-09-19 05:00:16
|
I have no idea. The website changes are done by another person, not me. -- Mgr. Jiří Činčura Independent IT Specialist On Fri, Sep 18, 2015, at 22:25, Nicolas F. Timmers wrote: > When version 4.8 will be available in the link > http://www.firebirdsql.org/en/additional-downloads/ > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Nicolas F. T. <nft...@ho...> - 2015-09-18 20:25:31
|
When version 4.8 will be available in the link http://www.firebirdsql.org/en/additional-downloads/ |
From: Jiří Č. <ji...@ci...> - 2015-09-17 18:02:34
|
I also tried to have the buffer bigger, because there's never enough performance. The tests are not mind-blowingly faster, but also not slower. And in _general_ bigger buffer (4k -> 32k in this case (https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/commit/ca24546ba96b55cf2122e8be6984bde1dd40a8d6)) means bigger bang. If anybody wants to give it a try, the build is here https://ci.appveyor.com/project/cincura_net/firebirdsql-data-firebirdclient/build/0.0.0.458 . -- Mgr. Jiří Činčura Independent IT Specialist |
From: Jiří Č. <ji...@ci...> - 2015-09-17 17:56:27
|
On Thu, Sep 17, 2015, at 17:57, Геннадий Забула wrote: > Narrowed the problem. The cause is a multithreaded update of the same > record field. Transactions, as I said don't dispatch the issue. The advice is simple. Don't update same record (not only in .NET; anywhere, anytool). :D -- Mgr. Jiří Činčura Independent IT Specialist |
From: Jiří Č. <ji...@ci...> - 2015-09-17 17:25:38
|
Async is not a problem either. There's still one pipe to server to work with. I did some preliminary testing and so far it works. Let's see where it ends. -- Mgr. Jiří Činčura Independent IT Specialist On Thu, Sep 17, 2015, at 16:13, Геннадий Забула wrote: > I've also looked at these streams but had left them alone. > Network stream works well with both Read and Write. But still not sure > about multithreaded Read/Write. BufferedStream internally uses one > buffer for both. > From > https://github.com/dotnet/coreclr/blob/master/src/mscorlib/src/System/IO/BufferedStream.cs > /// Class Invariants: > /// The class has one buffer, shared for reading & writing. > /// It can only be used for one or the other at any point in time - not > both. > Again, for current implementation using two streams is redundant, but > if async involved I can't tell anything. > > On 17 September 2015 at 16:51, Jiří Činčura <ji...@ci...> wrote: > > HI *, > > > > I'm looking at > > https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/blob/master/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version10/GdsConnection.cs#L136 > > and wondering why there's two streams? The underlying network stream > > (https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/blob/master/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version10/GdsConnection.cs#L204) > > is just one. > > > > There's no interleaving so why to have two. And also you can't have > > interleaving because you might have dangling buffer data (or rigorously > > flush, and that's back to no interleaving case). > > > > Or am I missing something? > > > > -- > > Mgr. Jiří Činčura > > Independent IT Specialist > > > > ------------------------------------------------------------------------------ > > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > > Get real-time metrics from all of your servers, apps and tools > > in one place. > > SourceForge users - Click here to start your Free Trial of Datadog now! > > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > > _______________________________________________ > > Firebird-net-provider mailing list > > Fir...@li... > > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Геннадий З. <zab...@gm...> - 2015-09-17 15:57:17
|
Narrowed the problem. The cause is a multithreaded update of the same record field. Transactions, as I said don't dispatch the issue. On 17 September 2015 at 17:38, Геннадий Забула <zab...@gm...> wrote: > lock conflict on no wait transaction > Acquire lock for relation (<Table with simultenous updates>) failed > ---> FirebirdSql.Data.Common.IscException: lock conflict on no wait > transaction > Acquire lock for relation (<Table with simultenous updates>) failed > > On 17 September 2015 at 17:38, Геннадий Забула <zab...@gm...> wrote: >> I was wrong about IsolationLevel. If use Isolationlevel.Serializable >> exception message changes to: >> >> On 17 September 2015 at 17:32, Геннадий Забула <zab...@gm...> wrote: >>> I'm trying to insert to database multiple items at once via following code: >>> >>> using (var transaction = >>> act.Database.BeginTransaction(System.Data.IsolationLevel.RepeatableRead)) >>> { >>> // inserting and updating several related entities. >>> act.SaveChanges() // Throws exception >>> } >>> >>> Exception message: >>> lock conflict on no wait transaction >>> deadlock >>> update conflicts with concurrent update >>> concurrent transaction number is 665378 >>> >>> A problematic query that throws is about updating the entity, that all >>> my queries update. >>> >>> Using any other IsolationLevel doesn't affect the behavior. |
From: Геннадий З. <zab...@gm...> - 2015-09-17 14:38:56
|
lock conflict on no wait transaction Acquire lock for relation (<Table with simultenous updates>) failed ---> FirebirdSql.Data.Common.IscException: lock conflict on no wait transaction Acquire lock for relation (<Table with simultenous updates>) failed On 17 September 2015 at 17:38, Геннадий Забула <zab...@gm...> wrote: > I was wrong about IsolationLevel. If use Isolationlevel.Serializable > exception message changes to: > > On 17 September 2015 at 17:32, Геннадий Забула <zab...@gm...> wrote: >> I'm trying to insert to database multiple items at once via following code: >> >> using (var transaction = >> act.Database.BeginTransaction(System.Data.IsolationLevel.RepeatableRead)) >> { >> // inserting and updating several related entities. >> act.SaveChanges() // Throws exception >> } >> >> Exception message: >> lock conflict on no wait transaction >> deadlock >> update conflicts with concurrent update >> concurrent transaction number is 665378 >> >> A problematic query that throws is about updating the entity, that all >> my queries update. >> >> Using any other IsolationLevel doesn't affect the behavior. |
From: Геннадий З. <zab...@gm...> - 2015-09-17 14:38:24
|
I was wrong about IsolationLevel. If use Isolationlevel.Serializable exception message changes to: On 17 September 2015 at 17:32, Геннадий Забула <zab...@gm...> wrote: > I'm trying to insert to database multiple items at once via following code: > > using (var transaction = > act.Database.BeginTransaction(System.Data.IsolationLevel.RepeatableRead)) > { > // inserting and updating several related entities. > act.SaveChanges() // Throws exception > } > > Exception message: > lock conflict on no wait transaction > deadlock > update conflicts with concurrent update > concurrent transaction number is 665378 > > A problematic query that throws is about updating the entity, that all > my queries update. > > Using any other IsolationLevel doesn't affect the behavior. |
From: Геннадий З. <zab...@gm...> - 2015-09-17 14:33:02
|
I'm trying to insert to database multiple items at once via following code: using (var transaction = act.Database.BeginTransaction(System.Data.IsolationLevel.RepeatableRead)) { // inserting and updating several related entities. act.SaveChanges() // Throws exception } Exception message: lock conflict on no wait transaction deadlock update conflicts with concurrent update concurrent transaction number is 665378 A problematic query that throws is about updating the entity, that all my queries update. Using any other IsolationLevel doesn't affect the behavior. |
From: Геннадий З. <zab...@gm...> - 2015-09-17 14:13:52
|
I've also looked at these streams but had left them alone. Network stream works well with both Read and Write. But still not sure about multithreaded Read/Write. BufferedStream internally uses one buffer for both. >From https://github.com/dotnet/coreclr/blob/master/src/mscorlib/src/System/IO/BufferedStream.cs /// Class Invariants: /// The class has one buffer, shared for reading & writing. /// It can only be used for one or the other at any point in time - not both. Again, for current implementation using two streams is redundant, but if async involved I can't tell anything. On 17 September 2015 at 16:51, Jiří Činčura <ji...@ci...> wrote: > HI *, > > I'm looking at > https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/blob/master/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version10/GdsConnection.cs#L136 > and wondering why there's two streams? The underlying network stream > (https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/blob/master/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version10/GdsConnection.cs#L204) > is just one. > > There's no interleaving so why to have two. And also you can't have > interleaving because you might have dangling buffer data (or rigorously > flush, and that's back to no interleaving case). > > Or am I missing something? > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Jiří Č. <ji...@ci...> - 2015-09-17 13:51:40
|
HI *, I'm looking at https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/blob/master/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version10/GdsConnection.cs#L136 and wondering why there's two streams? The underlying network stream (https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/blob/master/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version10/GdsConnection.cs#L204) is just one. There's no interleaving so why to have two. And also you can't have interleaving because you might have dangling buffer data (or rigorously flush, and that's back to no interleaving case). Or am I missing something? -- Mgr. Jiří Činčura Independent IT Specialist |
From: Mark J. (JIRA) <tr...@fi...> - 2015-09-15 09:31:16
|
Console application doesn't terminate when FB connection was used ----------------------------------------------------------------- Key: DNET-632 URL: http://tracker.firebirdsql.org/browse/DNET-632 Project: .NET Data provider Issue Type: Bug Components: ADO.NET Provider Affects Versions: 4.8.0.0 Environment: Windows 10, .NET 4.5, compiled with VS 2015 Reporter: Mark Junker Assignee: Jiri Cincura Attachments: TestClosingConnection.zip A once open FB connection keeps a console application from closing. It seems that the culprit is the pooling implementation. When I turn off pooling, the application closes as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Hajime N. <nak...@gm...> - 2015-09-15 01:31:10
|
2015-09-14 20:25 GMT+09:00 Jiří Činčura <ji...@ci...>: > > BTW you can also run the NUnit GUI and select the test(s) you want to > execute. I find it easier when doing interactive debugging. > > Thanks |
From: Jiří Č. <ji...@ci...> - 2015-09-14 15:37:24
|
On Mon, Sep 14, 2015, at 17:17, Геннадий Забула wrote: > How should this be implemented? My guess is by typing the code. ;) > I could take a look at this in the week. Sure, why not. The BOOLEAN in provider will not take much effort - I was checking it last year, quickly. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Mark R. <ma...@la...> - 2015-09-14 15:28:53
|
I have added a link to the initial implementation I did in Jaybird. It won't directly map to the C# implementation, but it might give you some indication of what needs to change where, and how it is encoded in the wire protocol. Mark On 14-9-2015 17:17, Геннадий Забула wrote: > How should this be implemented? > I could take a look at this in the week. > > On 14 September 2015 at 17:06, Jiri Cincura (JIRA) > <tr...@fi...> wrote: >> Support for BOOLEAN in FB3 >> -------------------------- >> >> Key: DNET-631 >> URL: http://tracker.firebirdsql.org/browse/DNET-631 >> Project: .NET Data provider >> Issue Type: Sub-task >> Components: ADO.NET Provider, DDEX Provider, Entity Framework support >> Affects Versions: 4.8.0.0 >> Reporter: Jiri Cincura >> Assignee: Jiri Cincura >> >> >> >> >> -- >> This message is automatically generated by JIRA. >> - >> If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa >> - >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Firebird-net-provider mailing list >> Fir...@li... >> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > -- Mark Rotteveel |
From: Геннадий З. <zab...@gm...> - 2015-09-14 15:17:46
|
How should this be implemented? I could take a look at this in the week. On 14 September 2015 at 17:06, Jiri Cincura (JIRA) <tr...@fi...> wrote: > Support for BOOLEAN in FB3 > -------------------------- > > Key: DNET-631 > URL: http://tracker.firebirdsql.org/browse/DNET-631 > Project: .NET Data provider > Issue Type: Sub-task > Components: ADO.NET Provider, DDEX Provider, Entity Framework support > Affects Versions: 4.8.0.0 > Reporter: Jiri Cincura > Assignee: Jiri Cincura > > > > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Jiri C. (JIRA) <tr...@fi...> - 2015-09-14 14:07:08
|
Support for BOOLEAN in FB3 -------------------------- Key: DNET-631 URL: http://tracker.firebirdsql.org/browse/DNET-631 Project: .NET Data provider Issue Type: Sub-task Components: ADO.NET Provider, DDEX Provider, Entity Framework support Affects Versions: 4.8.0.0 Reporter: Jiri Cincura Assignee: Jiri Cincura -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |