[Firebird-devel] [FB-Tracker] Created: (CORE-5433) Minor performance optimization - avoid additional database attachment from security objects mapping code
Minor performance optimization - avoid additional database attachment from security objects mapping code Key: CORE-5433 URL: http://tracker.firebirdsql.org/browse/CORE-5433 Project: Firebird Core Issue Type: Improvement Components: Engine Affects Versions: 3.0.1, 3.0.0, 4.0 Initial Reporter: Alexander Peshkov Make mapUser() function when invoked from Attachment::attachDatabase() use current (newly created) attachment instead of attaching to same database once more -- 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 -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Firebird 4 features
30.12.2016 18:05, Dimitry Sibiryakov wrote: > Do anybody object if I try to dig a little into CORE-5064? No, feel free. Dmitry -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Firebird 4 features
30.12.2016 15:59, Alex Peshkoff wrote: > Definitely not limited. But it's good idea to discuss new feature before > implementing it (specially if it's not already in the tracker). Ok. Do anybody object if I try to dig a little into CORE-5064? -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 15:52, Kovalenko Dmitry wrote: > No. It need for resolve a problem with cancelation of operations. > > http://tracker.firebirdsql.org/browse/CORE-5152 I'm sorry, but could you explain a little: how packet length can help in this case? > It will allow with minimal efforts detect the "op_cancel" operation in stream > of data packets at "SRVR_multi_thread" level. Does it mean that op_cancel packet can be send in the middle of any other packet? -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Firebird 4 features
On 12/30/16 17:54, Dimitry Sibiryakov wrote: > Hello, All. > > Is list of features for version 4 limited to listed in roadmap? > I.e. if I pull request for something else will it be rejected for sure? Definitely not limited. But it's good idea to discuss new feature before implementing it (specially if it's not already in the tracker). -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Firebird 4 features
Hello, All. Is list of features for version 4 limited to listed in roadmap? I.e. if I pull request for something else will it be rejected for sure? -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
>4) Knowledge of total length of packet is required only for current parser which need full packet to be in single buffer. If rewrite parser to use stateful automate, total length is needless. No. It need for resolve a problem with cancelation of operations. http://tracker.firebirdsql.org/browse/CORE-5152 Dmitry Kovalenko -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 12:19, Dimitry Sibiryakov wrote: > 1) Core team have no time for it. > 2) Core team have no time to review big patches from outsiders. > 3) Backward compatibility has to be kept. 4) Knowledge of total length of packet is required only for current parser which need full packet to be in single buffer. If rewrite parser to use stateful automate, total length is needless. -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 14:19, Dimitry Sibiryakov wrote: > > 1) Core team have no time for it. True. > 2) Core team have no time to review big patches from outsiders. Bullshit. > 3) Backward compatibility has to be kept. True. What a surprise! Dmitry -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 12:10, Kovalenko Dmitry wrote: >>From my point of view, protocol must be rewrited > > At minimum: > 1. The each packet should contain the field with own size. > 2. It is necessary to solve the problems with LazySend mode. 1) Core team have no time for it. 2) Core team have no time to review big patches from outsiders. 3) Backward compatibility has to be kept. -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
>From my point of view, protocol must be rewrited At minimum: 1. The each packet should contain the field with own size. 2. It is necessary to solve the problems with LazySend mode. Dmity Kovalenko www.ibprovider.com -Original Message- From: Mark Rotteveel [mailto:m...@lawinegevaar.nl] Sent: Monday, December 19, 2016 8:51 PM To: For discussion among Firebird Developers Subject: [Firebird-devel] Wire protocol changes in Firebird 4? Are there any wire protocol changes in Firebird 4 (or planned for Firebird 4). And if so, where can I find information on those changes? Mark -- Mark Rotteveel -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] [B3_0_Release] Can't compile in VS2015.
Fixed Regards, Vlad -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
