18.02.2019 17:18, liviuslivius wrote:
If you consider to remove it in CS only...
Nobody going to remove it, don't worry ;)
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
If you consider to remove it in CS only...I need it in super server personally
Regards,Karol Bieniaszewski
nullFirebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 18/02/2019 08:47, Adriano dos Santos Fernandes wrote:
> On 18/02/2019 08:37, Vlad Khorsun wrote:
>>
>> Seriously, if you (and others) consider it is important enough to
>> try to refresh
>> TIP cache in such cases - fill the ticket in tracker and i'll fix it.
>>
> If the change is going to app
18.02.2019 15:01, Vlad Khorsun wrote:
Second, Beta1 tag is already set so we need DY's opinion on this subject.
The tag will be moved today, but please don't commit before that. This
(even if fixed/changed) is not a showstopper.
Dmitry
Firebird-Devel mailing list, web interface at
https
18.02.2019 13:01, Alex Peshkoff via Firebird-devel wrote:
Just notice - if you do not use this function you will never have performance
issue with it.
It depends on the place where Vlad will put the TIP refresh to.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://list
18.02.2019 13:50, Dimitry Sibiryakov wrote:
18.02.2019 12:47, Adriano dos Santos Fernandes wrote:
If the change is going to appear only in Beta 2, then ok and I file a
ticket. Otherwise a ticket would not be necessary as the feature didn't
appeared in any alpha/beta release yet.
This change
On 2/18/19 2:57 PM, Dimitry Sibiryakov wrote:
18.02.2019 12:55, Alex Peshkoff via Firebird-devel wrote:
On the other hand this should better be fixed afterwards - design
where SS/CS provide different results is IMHO not good. Something
like awful borland's SPB items that provide useful results
18.02.2019 13:47, Adriano dos Santos Fernandes wrote:
On 18/02/2019 08:37, Vlad Khorsun wrote:
Seriously, if you (and others) consider it is important enough to
try to refresh
TIP cache in such cases - fill the ticket in tracker and i'll fix it.
If the change is going to appear only in Be
18.02.2019 12:55, Alex Peshkoff via Firebird-devel wrote:
On the other hand this should better be fixed afterwards - design where SS/CS provide
different results is IMHO not good. Something like awful borland's SPB items that provide
useful results only in SS. Well Borland can be excused here so
On 2/18/19 2:47 PM, Adriano dos Santos Fernandes wrote:
On 18/02/2019 08:37, Vlad Khorsun wrote:
Seriously, if you (and others) consider it is important enough to
try to refresh
TIP cache in such cases - fill the ticket in tracker and i'll fix it.
If the change is going to appear only in B
18.02.2019 12:47, Adriano dos Santos Fernandes wrote:
If the change is going to appear only in Beta 2, then ok and I file a
ticket. Otherwise a ticket would not be necessary as the feature didn't
appeared in any alpha/beta release yet.
This change AFAIU will make Firebird even slower than it
On 18/02/2019 08:37, Vlad Khorsun wrote:
>
>
> Seriously, if you (and others) consider it is important enough to
> try to refresh
> TIP cache in such cases - fill the ticket in tracker and i'll fix it.
>
If the change is going to appear only in Beta 2, then ok and I file a
ticket. Otherwise a tic
18.02.2019 13:19, Adriano dos Santos Fernandes wrote:
On 18/02/2019 05:50, Vlad Khorsun wrote:
18.02.2019 1:49, Adriano dos Santos Fernandes wrote:
Open two connections C1 and C2.
C2: select current_transaction from rdb$database; -- let's call the
result T2
C2: commit;
C1: select rdb$get_tran
On 18/02/2019 05:50, Vlad Khorsun wrote:
> 18.02.2019 1:49, Adriano dos Santos Fernandes wrote:
>> Open two connections C1 and C2.
>>
>> C2: select current_transaction from rdb$database; -- let's call the
>> result T2
>> C2: commit;
>>
>> C1: select rdb$get_transaction_cn(T2) from rdb$database;
>>
18.02.2019 1:49, Adriano dos Santos Fernandes wrote:
Open two connections C1 and C2.
C2: select current_transaction from rdb$database; -- let's call the
result T2
C2: commit;
C1: select rdb$get_transaction_cn(T2) from rdb$database;
In Super C1 returns the commit number. In Classic it returns N
15 matches
Mail list logo
