15.12.2015 12:54, Alex Peshkoff wrote:
> No. To change (or not) cache settings we need to know whether current
> user has DBO rights or not. And this becomes known only after the call
> to mapUser.
Do you mean cache settings written into database or memory cache settings?
I was sure that
On 12/14/2015 05:53 PM, Dimitry Sibiryakov wrote:
> 14.12.2015 15:48, Alex Peshkoff wrote:
>> On 12/14/2015 05:42 PM, Dimitry Sibiryakov wrote:
>>> 14.12.2015 15:39, Alex Peshkoff wrote:
>> Routine? not routine, but parameter in DPB makes it possible to decrease
cache size.
>>
On 12/15/2015 03:54 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 13:47, Alex Peshkoff wrote:
>> So you want to say that in case of CS there is no need in checking for
>> DBO and therefore calling mapUser too early? Seems to be so.
> And in the case of SS, if error "not enough rights" is thrown,
On 12/15/2015 02:58 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 12:54, Alex Peshkoff wrote:
>> No. To change (or not) cache settings we need to know whether current
>> user has DBO rights or not. And this becomes known only after the call
>> to mapUser.
> Do you mean cache settings written into
15.12.2015 13:47, Alex Peshkoff wrote:
> So you want to say that in case of CS there is no need in checking for
> DBO and therefore calling mapUser too early? Seems to be so.
And in the case of SS, if error "not enough rights" is thrown, then the
connection
failed, database is unloaded,
15.12.2015 14:35, Alex Peshkoff wrote:
> When database is opened by SS and
> is ready for processing mapping request it can be used by another
> attachment - and it will be used with wrong cache settings, which may
> badly affect performance.
What do you think about this:
1) For first
15.12.2015 13:54, Dimitry Sibiryakov wrote:
> if error "not enough rights" is thrown, then the connection
> failed, database is unloaded, cache setting are reset.
All this is in the case if dynamic cache size grow is impossible, of course.
--
WBR, SD.
On 12/15/2015 04:50 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 14:35, Alex Peshkoff wrote:
>>When database is opened by SS and
>> is ready for processing mapping request it can be used by another
>> attachment - and it will be used with wrong cache settings, which may
>> badly affect
15.12.2015 14:57, Alex Peshkoff wrote:
> Single additional attachment once per server operation is not worth
> wasting time on it.
You are wrong here.
--
WBR, SD.
--
Firebird-Devel mailing list, web interface at
On 12/15/2015 05:12 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 14:57, Alex Peshkoff wrote:
>> Single additional attachment once per server operation is not worth
>> wasting time on it.
> You are wrong here.
>
Таки я с этой дискуссией завязываю - ибо она пошла без аргументов.
И с остальной
On 12/14/2015 05:42 PM, Dimitry Sibiryakov wrote:
> 14.12.2015 15:39, Alex Peshkoff wrote:
Routine? not routine, but parameter in DPB makes it possible to decrease
>> cache size.
If you make the routine to work with already loaded database, these
parameters will be
On 12/14/2015 04:33 PM, Dimitry Sibiryakov wrote:
> 14.12.2015 14:27, Alex Peshkoff wrote:
>> Vlad promised to do some changes in CCH required to fix this issue.
> Wouldn't be enough to shift the call of the routine a bit down, at the
> place where dbb
> is completely initialized to prevent
On 12/14/2015 05:34 PM, Dimitry Sibiryakov wrote:
> 14.12.2015 15:25, Alex Peshkoff wrote:
>> On 12/14/2015 05:15 PM, Dimitry Sibiryakov wrote:
>>> 14.12.2015 15:10, Alex Peshkoff wrote:
in a case when cache to be decreased reopen is unavoidable.
>>> Errr... Cache? What this routine
14.12.2015 15:10, Alex Peshkoff wrote:
> in a case when cache to be decreased reopen is unavoidable.
Errr... Cache? What this routine does at all?
--
WBR, SD.
--
Firebird-Devel mailing list, web interface at
14.12.2015 14:04, Alex Peshkoff wrote:
>> 1) Slow connect
> Connect second time - you will not see this effect for SS & SC, for CS
> it's known problem.
Is it in tracker? Is it going to be fixed?
--
WBR, SD.
--
On 12/14/2015 05:15 PM, Dimitry Sibiryakov wrote:
> 14.12.2015 15:10, Alex Peshkoff wrote:
>> in a case when cache to be decreased reopen is unavoidable.
> Errr... Cache? What this routine does at all?
>
Routine? not routine, but parameter in DPB makes it possible to decrease
cache size.
14.12.2015 15:25, Alex Peshkoff wrote:
> On 12/14/2015 05:15 PM, Dimitry Sibiryakov wrote:
>> 14.12.2015 15:10, Alex Peshkoff wrote:
>>> in a case when cache to be decreased reopen is unavoidable.
>> Errr... Cache? What this routine does at all?
>
> Routine? not routine, but parameter in DPB
14.12.2015 15:48, Alex Peshkoff wrote:
> On 12/14/2015 05:42 PM, Dimitry Sibiryakov wrote:
>> 14.12.2015 15:39, Alex Peshkoff wrote:
> Routine? not routine, but parameter in DPB makes it possible to decrease
>>> cache size.
> If you make the routine to work with already loaded
14.12.2015 15:39, Alex Peshkoff wrote:
>>> Routine? not routine, but parameter in DPB makes it possible to decrease
>>> >>cache size.
>> > If you make the routine to work with already loaded database, these
>> > parameters will be
>> >already applied before it is called, no?
>> >
> No.
Hello, All.
Trying to understand why crypt key is requested several times during one
connect to a
database, I added some logging into cryptomanager and got following log:
> SD-HP Sat Dec 12 19:02:17 2015
> 02016F20 crypt manager loaded AES128
> SD-HP Sat Dec 12 19:02:17 2015
>
20 matches
Mail list logo
