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: Геннадий З. <zab...@gm...> - 2015-10-14 16:04:18
|
PR on github was updated On 7 October 2015 at 10:36, Hennadii Zabula (JIRA) <tr...@fi...> wrote: > Add exception when FbConnectionPoolManager.ClearPools used inapropriately > ------------------------------------------------------------------------- > > Key: DNET-638 > URL: http://tracker.firebirdsql.org/browse/DNET-638 > Project: .NET Data provider > Issue Type: Improvement > Components: ADO.NET Provider > Affects Versions: vNext > Reporter: Hennadii Zabula > Assignee: Jiri Cincura > > > We had run in a problem where currently running queries were failing because another thread wrongly cleared all pools. It was quite unexpected. > > We fixed the issue in our code with the thread, but I think it should throw InvalidOperationException if _busy dictionary is not empty, because it means that there may be currently running queries. > > The exception could add information about the problems caused by an inappropriate call to ClearPool. > > > -- > 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 > > > > ------------------------------------------------------------------------------ > Full-scale, agent-less Infrastructure Monitoring from a single dashboard > Integrate with 40+ ManageEngine ITSM Solutions for complete visibility > Physical-Virtual-Cloud Infrastructure monitoring from one console > Real user monitoring with APM Insights and performance trend reports > Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140 > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Michał Z. <mz...@e-...> - 2015-10-14 09:42:33
|
Hi! I've made a pull request on github with my proposal. Cheers! Michał 2015-10-14 7:52 GMT+02:00 Jiří Činčura <ji...@ci...>: > On Tue, Oct 13, 2015, at 22:53, Michał Ziemski wrote: > > I would rather also test connectionString.MaxPoolSize with the > > "_available" > > stack > > and not the "_busy" list. This would make connectionString.MaxPoolSize > > You mean: > if (_available.Count() + 1 > connectionString.MaxPoolSize) > throw new > > InvalidOperationException("Connection > pool is full."); > ? > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > |
From: Jiří Č. <ji...@ci...> - 2015-10-14 05:52:50
|
On Tue, Oct 13, 2015, at 22:53, Michał Ziemski wrote: > I would rather also test connectionString.MaxPoolSize with the > "_available" > stack > and not the "_busy" list. This would make connectionString.MaxPoolSize You mean: if (_available.Count() + 1 > connectionString.MaxPoolSize) throw new InvalidOperationException("Connection pool is full."); ? -- Mgr. Jiří Činčura Independent IT Specialist |
From: Michał Z. <mz...@e-...> - 2015-10-13 21:15:40
|
Hi! I've jest run into a problem with the connection pool. When I reach the limit an exception is thrown. It seems to me as an suboptimal thing to di in such a case. Con pool is there to gain speed and random exceptions are IMHO too high a price to pay. I think in such a case new connections should be opened and added to the pool. connectionString.MaxPoolSize should decide whether the connection is returned to the pool or closed. I would rather also test connectionString.MaxPoolSize with the "_available" stack and not the "_busy" list. This would make connectionString.MaxPoolSize mean "how many connections you would like to have at hand when you're working with the database" rather than "how many concurrent connections would you like to allow", which I think is closer to the goal of the pool. Such behaviour would be much more predictable to the user. Cheers! Michał Ziemski |
From: Jiří Č. <ji...@ci...> - 2015-10-13 09:38:47
|
On Tue, Oct 13, 2015, at 11:08, Mercea Paul wrote: > Table unknown > > EdmMetadata Turn off initializers. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Mercea P. <pau...@al...> - 2015-10-13 09:27:36
|
Hi all I have ported an application (MVC5, SQLServer) to Firebird but i notice some exceptions in debug mode (tried fb 4.7 and fb 4.8 provider). This app is using AspNet.Identity to authenticate users. With SQLServer i didn't get this exception: An exception of type 'FirebirdSql.Data.FirebirdClient.FbException' occurred in FirebirdSql.Data.FirebirdClient.dll but was not handled in user code Additional information: Dynamic SQL Error SQL error code = -204 Table unknown EdmMetadata At line 5, column 19 Any hint about this? TIA Paul Mercea |
From: Hennadii Z. (JIRA) <tr...@fi...> - 2015-10-07 07:37:08
|
Add exception when FbConnectionPoolManager.ClearPools used inapropriately ------------------------------------------------------------------------- Key: DNET-638 URL: http://tracker.firebirdsql.org/browse/DNET-638 Project: .NET Data provider Issue Type: Improvement Components: ADO.NET Provider Affects Versions: vNext Reporter: Hennadii Zabula Assignee: Jiri Cincura We had run in a problem where currently running queries were failing because another thread wrongly cleared all pools. It was quite unexpected. We fixed the issue in our code with the thread, but I think it should throw InvalidOperationException if _busy dictionary is not empty, because it means that there may be currently running queries. The exception could add information about the problems caused by an inappropriate call to ClearPool. -- 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: Jiří Č. <ji...@ci...> - 2015-10-06 18:14:15
|
On Tue, Oct 6, 2015, at 20:12, Геннадий Забула wrote: > Of course. But exception could provide additional information about > what is going on and where do I need to look. Maybe put that into tracker and others can vote. We'll see. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Геннадий З. <zab...@gm...> - 2015-10-06 18:12:18
|
> Well, when you clear your pool and other threads are running queries you're the one responsible. :) Of course. But exception could provide additional information about what is going on and where do I need to look. On 6 October 2015 at 19:46, Jiří Činčura <ji...@ci...> wrote: > On Tue, Oct 6, 2015, at 15:46, Геннадий Забула wrote: >> I have a question about method implementation. >> CleanConnectionsImpl >> It cleans connections in pool. >> But why _busy dictionary connections are disposed as well? >> Isn't it a trouble maker for inappropriate ClearPools method users? >> >> We had run in a problem where currently running queries were failing >> because another thread wrongly cleared all pools. It was quite >> unexpected. > > Well, when you clear your pool and other threads are running queries > you're the one responsible. :) > >> We fixed the issue in our code with the thread, but I think it should >> throw InvalidOperationException if _busy dictionary is not empty, >> because it means that there may be currently running queries. > > I don't have problem throwing exception, because for valid uses it > changes nothing. But might be unexpected when somebody took advantage of > that behavior. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Jiří Č. <ji...@ci...> - 2015-10-06 16:58:16
|
Talking about corner cases. Would anybody here mind sending me some statements that mix comments, literals, SET TERMs, etc. in some crazy ways? I think the new parser - which handles comments and is also faster - is getting ready to real tests. :) -- Mgr. Jiří Činčura Independent IT Specialist |
From: Jiří Č. <ji...@ci...> - 2015-10-06 16:46:26
|
On Tue, Oct 6, 2015, at 15:46, Геннадий Забула wrote: > I have a question about method implementation. > CleanConnectionsImpl > It cleans connections in pool. > But why _busy dictionary connections are disposed as well? > Isn't it a trouble maker for inappropriate ClearPools method users? > > We had run in a problem where currently running queries were failing > because another thread wrongly cleared all pools. It was quite > unexpected. Well, when you clear your pool and other threads are running queries you're the one responsible. :) > We fixed the issue in our code with the thread, but I think it should > throw InvalidOperationException if _busy dictionary is not empty, > because it means that there may be currently running queries. I don't have problem throwing exception, because for valid uses it changes nothing. But might be unexpected when somebody took advantage of that behavior. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Геннадий З. <zab...@gm...> - 2015-10-06 13:46:31
|
I have a question about method implementation. CleanConnectionsImpl It cleans connections in pool. But why _busy dictionary connections are disposed as well? Isn't it a trouble maker for inappropriate ClearPools method users? We had run in a problem where currently running queries were failing because another thread wrongly cleared all pools. It was quite unexpected. We fixed the issue in our code with the thread, but I think it should throw InvalidOperationException if _busy dictionary is not empty, because it means that there may be currently running queries. |
From: Jiří Č. <ji...@ci...> - 2015-10-06 11:55:28
|
On Tue, Oct 6, 2015, at 13:16, Amro wrote: > To get more concrete can you provide examples of all relevant corner > cases? If I would knew all of them it would not be corner case. It's just a lot of playing. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Amro <amr...@gm...> - 2015-10-06 11:15:38
|
Jiri, To get more concrete can you provide examples of all relevant corner cases? -----Ursprüngliche Nachricht----- Von: Jiří Činčura [mailto:ji...@ci...] Gesendet: Dienstag, 6. Oktober 2015 06:37 An: For users and developers of the Firebird .NET providers <fir...@li...> Betreff: Re: [Firebird-net-provider] Parser class/library On Mon, Oct 5, 2015, at 21:32, Michał Ziemski wrote: > IMHO you won't be able to handle all the corner cases without full > grammar parser. Well, the cases we need are not that wide. But it's tedious anyway. > For example consider a "SET TERM" inside an "EXECUTE BLOCK". > Lacking the grammar understnding you won't recognize that as an > invalid term in the execute block and you'll simply cut the block in > half. So the decision is how far do you I don't care much about invalid scripts. It fails either way. But I agree that it's at least confusing for people consuming the library. > want > to go. Personally, not far. :) There's way more interesting pieces. > Writing a full scale parser for FB SQL in a rather easy but very > tedious and time-consuming task. > Having that as a tool would be a great addition to FB ecosystem. > The parser in FB itself is written in yacc so it's faily transportable. > Sill you'll have to go rule by rule > and convert to C#. > Actually I have tried this myself in F# (it's far far better suited > for > parsers) and am about 50% through. > I would gladly donate the code if you'd be interested. I don't think it will hurt. > If you would preffer the faster approach I would suggest: > - a simple lexer by hand that recognizes tokens "SET" "TERM" > CURRENT_TERM_SYMBOL "--" , NEWLINE OTHER_TOKEN and STRING > - a parser that iterates the tokens form lexer, tests for sequences: > "SET" "TERM" OTHER_TOKEN CURRENT_TERM_SYMBOL - to set new terms > CURRENT_TERM_SYMBOL - to yield accumulated OTHER_TOKENs and STRINGs > - -- to start a comment and skip everything till NEWLINE this should > be an easy enough state machine to write by hand. That's what I'm currently doing. Sadly. -- Mgr. Jiří Činčura Independent IT Specialist ------------------------------------------------------------------------------ _______________________________________________ Firebird-net-provider mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Alexander Muylaert-G. <amu...@ho...> - 2015-10-06 05:44:41
|
I know we are sponsoring This... But it sounds to me like so much work and so little gain. Sure, the current parse thing is slow and buggy, but only a few minor bugs and performance gain Will be limited as well. I think looking at 3th party parsers isn,'t a bad idea at All. Sent from my Windows Phone ________________________________ From: Jiří Činčura<mailto:ji...@ci...> Sent: 6/10/2015 6:38 To: For users and developers of the Firebird .NET providers<mailto:fir...@li...> Subject: Re: [Firebird-net-provider] Parser class/library On Mon, Oct 5, 2015, at 21:32, Michał Ziemski wrote: > IMHO you won't be able to handle all the corner cases without full > grammar > parser. Well, the cases we need are not that wide. But it's tedious anyway. > For example consider a "SET TERM" inside an "EXECUTE BLOCK". > Lacking the grammar understnding you won't recognize that as an invalid > term in the execute block and > you'll simply cut the block in half. So the decision is how far do you I don't care much about invalid scripts. It fails either way. But I agree that it's at least confusing for people consuming the library. > want > to go. Personally, not far. :) There's way more interesting pieces. > Writing a full scale parser for FB SQL in a rather easy but very tedious > and time-consuming task. > Having that as a tool would be a great addition to FB ecosystem. > The parser in FB itself is written in yacc so it's faily transportable. > Sill you'll have to go rule by rule > and convert to C#. > Actually I have tried this myself in F# (it's far far better suited for > parsers) and am about 50% through. > I would gladly donate the code if you'd be interested. I don't think it will hurt. > If you would preffer the faster approach I would suggest: > - a simple lexer by hand that recognizes tokens "SET" "TERM" > CURRENT_TERM_SYMBOL "--" , NEWLINE OTHER_TOKEN and STRING > - a parser that iterates the tokens form lexer, tests for sequences: > "SET" "TERM" OTHER_TOKEN CURRENT_TERM_SYMBOL - to set new terms > CURRENT_TERM_SYMBOL - to yield accumulated OTHER_TOKENs and STRINGs > - -- to start a comment and skip everything till NEWLINE > this should be an easy enough state machine to write by hand. That's what I'm currently doing. Sadly. -- Mgr. Jiří Činčura Independent IT Specialist ------------------------------------------------------------------------------ _______________________________________________ Firebird-net-provider mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Jiří Č. <ji...@ci...> - 2015-10-06 04:37:25
|
On Mon, Oct 5, 2015, at 21:32, Michał Ziemski wrote: > IMHO you won't be able to handle all the corner cases without full > grammar > parser. Well, the cases we need are not that wide. But it's tedious anyway. > For example consider a "SET TERM" inside an "EXECUTE BLOCK". > Lacking the grammar understnding you won't recognize that as an invalid > term in the execute block and > you'll simply cut the block in half. So the decision is how far do you I don't care much about invalid scripts. It fails either way. But I agree that it's at least confusing for people consuming the library. > want > to go. Personally, not far. :) There's way more interesting pieces. > Writing a full scale parser for FB SQL in a rather easy but very tedious > and time-consuming task. > Having that as a tool would be a great addition to FB ecosystem. > The parser in FB itself is written in yacc so it's faily transportable. > Sill you'll have to go rule by rule > and convert to C#. > Actually I have tried this myself in F# (it's far far better suited for > parsers) and am about 50% through. > I would gladly donate the code if you'd be interested. I don't think it will hurt. > If you would preffer the faster approach I would suggest: > - a simple lexer by hand that recognizes tokens "SET" "TERM" > CURRENT_TERM_SYMBOL "--" , NEWLINE OTHER_TOKEN and STRING > - a parser that iterates the tokens form lexer, tests for sequences: > "SET" "TERM" OTHER_TOKEN CURRENT_TERM_SYMBOL - to set new terms > CURRENT_TERM_SYMBOL - to yield accumulated OTHER_TOKENs and STRINGs > - -- to start a comment and skip everything till NEWLINE > this should be an easy enough state machine to write by hand. That's what I'm currently doing. Sadly. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Michał Z. <mz...@e-...> - 2015-10-05 19:58:33
|
Hi! IMHO you won't be able to handle all the corner cases without full grammar parser. For example consider a "SET TERM" inside an "EXECUTE BLOCK". Lacking the grammar understnding you won't recognize that as an invalid term in the execute block and you'll simply cut the block in half. So the decision is how far do you want to go. Writing a full scale parser for FB SQL in a rather easy but very tedious and time-consuming task. Having that as a tool would be a great addition to FB ecosystem. The parser in FB itself is written in yacc so it's faily transportable. Sill you'll have to go rule by rule and convert to C#. Actually I have tried this myself in F# (it's far far better suited for parsers) and am about 50% through. I would gladly donate the code if you'd be interested. If you would preffer the faster approach I would suggest: - a simple lexer by hand that recognizes tokens "SET" "TERM" CURRENT_TERM_SYMBOL "--" , NEWLINE OTHER_TOKEN and STRING - a parser that iterates the tokens form lexer, tests for sequences: "SET" "TERM" OTHER_TOKEN CURRENT_TERM_SYMBOL - to set new terms CURRENT_TERM_SYMBOL - to yield accumulated OTHER_TOKENs and STRINGs - -- to start a comment and skip everything till NEWLINE this should be an easy enough state machine to write by hand. Cheers! Michał 2015-10-05 15:30 GMT+02:00 Jiří Činčura <ji...@ci...>: > Hi, > > I'm working on a bug fix for DNET-266. And the more and more I tweak the > parser I wrote this morning to properly handle all the edge cases I'm > wondering whether it would make sense to take a dependency on some > library or class that can do some basic parsing. We don't need full > grammar features like ANTLR, just something that can tokenize SQL and > handle comments (or in general tokenizer with "escaping" support). > > What do you think? Any recommendations? > > BTW the bugfix is sponsored by SMS-Timing. Kudos to them. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > |
From: Amro El-F. <amr...@gm...> - 2015-10-05 15:01:25
|
True, but in order for yacc (or antlr) to generate C# code you have to use their syntax. This syntax is used to provide the so called grammar mentioned by Jiri. In General those kind of tools are basically small "compilers" which parses a given piece of "grammar" and then construct lexical analyzers. Changes in the syntax of the "grammar" tends to be breaking changes by nature! > -----Ursprüngliche Nachricht----- > Von: Геннадий Забула [mailto:zab...@gm...] > Gesendet: Montag, 5. Oktober 2015 16:43 > An: For users and developers of the Firebird .NET providers <firebird-net- > pro...@li...> > Betreff: Re: [Firebird-net-provider] Parser class/library > > IIRC, yacc\lex are an external tools that produce .cs files that provide parsing. > > > On 5 October 2015 at 17:31, Amro El-Fakharany <amr...@gm...> > wrote: > > I would be very careful taking a dependency on an external library like yacc > or antlr and would recommend to avoid such a path. > > If at all a standalone "light weight" tokenizer should be preferable > although, unfortunately, I don’t know any. > > Libraries like antlr and yacc are simply awesome but changes in such > libraries tends to be breaking changes! > > > > > >> -----Ursprüngliche Nachricht----- > >> Von: Геннадий Забула [mailto:zab...@gm...] > >> Gesendet: Montag, 5. Oktober 2015 16:22 > >> An: For users and developers of the Firebird .NET providers > >> <firebird-net- pro...@li...> > >> Betreff: Re: [Firebird-net-provider] Parser class/library > >> > >> EF uses yacc and lex for EntityTree parsing. > >> They both produce C# class that can be compiled into the assembly. > >> > >> On 5 October 2015 at 16:30, Jiří Činčura <ji...@ci...> wrote: > >> > Hi, > >> > > >> > I'm working on a bug fix for DNET-266. And the more and more I > >> > tweak the parser I wrote this morning to properly handle all the > >> > edge cases I'm wondering whether it would make sense to take a > >> > dependency on > >> some > >> > library or class that can do some basic parsing. We don't need full > >> > grammar features like ANTLR, just something that can tokenize SQL > >> > and handle comments (or in general tokenizer with "escaping" support). > >> > > >> > What do you think? Any recommendations? > >> > > >> > BTW the bugfix is sponsored by SMS-Timing. Kudos to them. > >> > > >> > -- > >> > Mgr. Jiří Činčura > >> > Independent IT Specialist > >> > > >> > ------------------------------------------------------------------- > >> > --- > >> > -------- _______________________________________________ > >> > 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 > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Геннадий З. <zab...@gm...> - 2015-10-05 14:43:26
|
IIRC, yacc\lex are an external tools that produce .cs files that provide parsing. On 5 October 2015 at 17:31, Amro El-Fakharany <amr...@gm...> wrote: > I would be very careful taking a dependency on an external library like yacc or antlr and would recommend to avoid such a path. > If at all a standalone "light weight" tokenizer should be preferable although, unfortunately, I don’t know any. > Libraries like antlr and yacc are simply awesome but changes in such libraries tends to be breaking changes! > > >> -----Ursprüngliche Nachricht----- >> Von: Геннадий Забула [mailto:zab...@gm...] >> Gesendet: Montag, 5. Oktober 2015 16:22 >> An: For users and developers of the Firebird .NET providers <firebird-net- >> pro...@li...> >> Betreff: Re: [Firebird-net-provider] Parser class/library >> >> EF uses yacc and lex for EntityTree parsing. >> They both produce C# class that can be compiled into the assembly. >> >> On 5 October 2015 at 16:30, Jiří Činčura <ji...@ci...> wrote: >> > Hi, >> > >> > I'm working on a bug fix for DNET-266. And the more and more I tweak >> > the parser I wrote this morning to properly handle all the edge cases >> > I'm wondering whether it would make sense to take a dependency on >> some >> > library or class that can do some basic parsing. We don't need full >> > grammar features like ANTLR, just something that can tokenize SQL and >> > handle comments (or in general tokenizer with "escaping" support). >> > >> > What do you think? Any recommendations? >> > >> > BTW the bugfix is sponsored by SMS-Timing. Kudos to them. >> > >> > -- >> > Mgr. Jiří Činčura >> > Independent IT Specialist >> > >> > ---------------------------------------------------------------------- >> > -------- _______________________________________________ >> > 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: Amro El-F. <amr...@gm...> - 2015-10-05 14:31:54
|
I would be very careful taking a dependency on an external library like yacc or antlr and would recommend to avoid such a path. If at all a standalone "light weight" tokenizer should be preferable although, unfortunately, I don’t know any. Libraries like antlr and yacc are simply awesome but changes in such libraries tends to be breaking changes! > -----Ursprüngliche Nachricht----- > Von: Геннадий Забула [mailto:zab...@gm...] > Gesendet: Montag, 5. Oktober 2015 16:22 > An: For users and developers of the Firebird .NET providers <firebird-net- > pro...@li...> > Betreff: Re: [Firebird-net-provider] Parser class/library > > EF uses yacc and lex for EntityTree parsing. > They both produce C# class that can be compiled into the assembly. > > On 5 October 2015 at 16:30, Jiří Činčura <ji...@ci...> wrote: > > Hi, > > > > I'm working on a bug fix for DNET-266. And the more and more I tweak > > the parser I wrote this morning to properly handle all the edge cases > > I'm wondering whether it would make sense to take a dependency on > some > > library or class that can do some basic parsing. We don't need full > > grammar features like ANTLR, just something that can tokenize SQL and > > handle comments (or in general tokenizer with "escaping" support). > > > > What do you think? Any recommendations? > > > > BTW the bugfix is sponsored by SMS-Timing. Kudos to them. > > > > -- > > Mgr. Jiří Činčura > > Independent IT Specialist > > > > ---------------------------------------------------------------------- > > -------- _______________________________________________ > > 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-10-05 14:23:38
|
http://entityframework.codeplex.com/SourceControl/latest#src/EntityFramework/Core/Common/EntitySql/GenerateParser.cmd On 5 October 2015 at 17:22, Геннадий Забула <zab...@gm...> wrote: > EF uses yacc and lex for EntityTree parsing. > They both produce C# class that can be compiled into the assembly. > > On 5 October 2015 at 16:30, Jiří Činčura <ji...@ci...> wrote: >> Hi, >> >> I'm working on a bug fix for DNET-266. And the more and more I tweak the >> parser I wrote this morning to properly handle all the edge cases I'm >> wondering whether it would make sense to take a dependency on some >> library or class that can do some basic parsing. We don't need full >> grammar features like ANTLR, just something that can tokenize SQL and >> handle comments (or in general tokenizer with "escaping" support). >> >> What do you think? Any recommendations? >> >> BTW the bugfix is sponsored by SMS-Timing. Kudos to them. >> >> -- >> Mgr. Jiří Činčura >> Independent IT Specialist >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Firebird-net-provider mailing list >> Fir...@li... >> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Геннадий З. <zab...@gm...> - 2015-10-05 14:22:35
|
EF uses yacc and lex for EntityTree parsing. They both produce C# class that can be compiled into the assembly. On 5 October 2015 at 16:30, Jiří Činčura <ji...@ci...> wrote: > Hi, > > I'm working on a bug fix for DNET-266. And the more and more I tweak the > parser I wrote this morning to properly handle all the edge cases I'm > wondering whether it would make sense to take a dependency on some > library or class that can do some basic parsing. We don't need full > grammar features like ANTLR, just something that can tokenize SQL and > handle comments (or in general tokenizer with "escaping" support). > > What do you think? Any recommendations? > > BTW the bugfix is sponsored by SMS-Timing. Kudos to them. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider |
From: Jiří Č. <ji...@ci...> - 2015-10-05 13:30:37
|
Hi, I'm working on a bug fix for DNET-266. And the more and more I tweak the parser I wrote this morning to properly handle all the edge cases I'm wondering whether it would make sense to take a dependency on some library or class that can do some basic parsing. We don't need full grammar features like ANTLR, just something that can tokenize SQL and handle comments (or in general tokenizer with "escaping" support). What do you think? Any recommendations? BTW the bugfix is sponsored by SMS-Timing. Kudos to them. -- Mgr. Jiří Činčura Independent IT Specialist |
From: Ivan I. (JIRA) <tr...@fi...> - 2015-10-02 20:10:19
|
Reconnect to another FireBird DB without exiting from an Application -------------------------------------------------------------------- Key: DNET-637 URL: http://tracker.firebirdsql.org/browse/DNET-637 Project: .NET Data provider Issue Type: Task Components: ADO.NET Provider Affects Versions: 4.7.0.0 Environment: Visual Studio 2010, .NET 4.0 Visual Basic Reporter: Ivan Ivanovich Assignee: Jiri Cincura I have connected to FB Database using FBConnection class and Retreive Data using FBDataAdapter. ALL Go OK. Now I need to close current connection and connect to another FB Database without exiting a Program. I do it by issuing the code below: Public FB_Con As FBConnection FB_Con = New FBConnection '-------------Processing Data FB_Con.Close() FbConnection.ClearPool(FB_Con) FB_Con.Dispose() Then I issue FB_Con.Open with new connection string (to another FB Database) I want to be careful with the other users, which are connected to FB server. Is this variant is good and careful? -- 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: Jiří Č. <ji...@ci...> - 2015-10-02 07:02:12
|
On Fri, Oct 2, 2015, at 08:12, Геннадий Забула wrote: > It will cover the case where you use mixed scheme: all tables have one > generator, except several that have per table generators. You specify > context-wide implementation per database generator, and in > ModelBuilder you specify generators for these exceptional tables. Simple convention? -- Mgr. Jiří Činčura Independent IT Specialist |