15.01.2017 19:00, Adriano dos Santos Fernandes wrote:
> So what I call virtual metadata and how would it solve the problems:
Sounds not bad, but requires more programming and is less effective than
versioned
metadata cache.
> When a DDL command is issued, it will not change metadata
On 01/15/17 12:24, Damyan Ivanov wrote:
> -=| Alex Peshkoff, 13.01.2017 14:32:09 +0300 |=-
>> On 01/03/17 00:38, Damyan Ivanov wrote:
>>> I've been chasing this for some time, and finally I've come (with help
>>> from others) to a environment which makes the segfault relatively easy
>>> to
Em 15/01/2017 12:53, Dimitry Sibiryakov escreveu:
> 15.01.2017 15:50, Adriano dos Santos Fernandes wrote:
>> What is our maximum code right margin?
>
> http://www.firebirdsql.org/en/coding-style/
>
>
Its funny that it's not where it need to be: README.coding.style.
Adriano
All,
First, must say this is based on state-of-the-art modern architecture of
a different field: web libraries/frameworks, using the Virtual DOM.
First, the (Firebird) problem, but I'll abstain to comment internal
details of DFW.
About multiple Firebird metadata update (DDL commands) in the
15.01.2017 17:50, Adriano dos Santos Fernandes wrote:
> What is our maximum code right margin?
>
> AFAIK it used to be 100 and I remember some discussion to increase it.
>
> Some people is thinking it's infinite.
>
> I think currently 100 is too low and 120 would be better.
It used to be 80 and
15.01.2017 15:50, Adriano dos Santos Fernandes wrote:
> What is our maximum code right margin?
http://www.firebirdsql.org/en/coding-style/
--
WBR, SD.
--
Developer Access Program for Intel Xeon Phi Processors
What is our maximum code right margin?
AFAIK it used to be 100 and I remember some discussion to increase it.
Some people is thinking it's infinite.
I think currently 100 is too low and 120 would be better.
Adriano
I have a test in Jaybird that post multiple events
(https://github.com/FirebirdSQL/jaybird/blob/master/src/test/org/firebirdsql/event/TestFBEventManager.java#L173)
Essentially it inserts on multiple threads (100 inserts per thread, 5
threads, a commit after each insert) which causes a trigger
15.01.2017 11:53, Mark Rotteveel wrote:
> The windows build of Firebird 3 is broken (note: I haven't checked the
> Firebird 4 build, might have the same problem).
>
> It fails when building gpre_boot, this failure is introduced in:
>
> commit 40f782ae3e918c4f3842571ff8064be1c4f54961
> Author:
The windows build of Firebird 3 is broken (note: I haven't checked the
Firebird 4 build, might have the same problem).
It fails when building gpre_boot, this failure is introduced in:
commit 40f782ae3e918c4f3842571ff8064be1c4f54961
Author: AlexPeshkoff
Date: Fri Jan 13
-=| Alex Peshkoff, 13.01.2017 14:32:09 +0300 |=-
> On 01/03/17 00:38, Damyan Ivanov wrote:
> > I've been chasing this for some time, and finally I've come (with help
> > from others) to a environment which makes the segfault relatively easy
> > to reproduce, although it still requires patience.
>
ALTER DOMAIN DROP CONSTRAINT and ADD CHECK too slow
---
Key: CORE-5453
URL: http://tracker.firebirdsql.org/browse/CORE-5453
Project: Firebird Core
Issue Type: Bug
Affects Versions: 2.5.6
12 matches
Mail list logo