Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 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. http://tracker.firebirdsql.org/browse/CORE-6003 Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 AFAIU will make Firebird even slower than it is now. It could make slower RDB$GET_TRANSACTION_CN only and only if its argument is larger than cached Next marker. I.e. it will not affect normal engine operations. Regards, Vlad Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 only in SS. Well Borland can be excused here somehow - they were going to drop CS support. But ee are not goint to do it . May be the best fix would be to remove subj function? I see no practical usage for it in real applications. Do you? Not sure. Just notice - if you do not use this function you will never have performance issue with it. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 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. First, i need more opinions\agreement if this change is really required. Second, Beta1 tag is already set so we need DY's opinion on this subject. Regards, Vlad Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 somehow - they were going to drop CS support. But ee are not goint to do it . May be the best fix would be to remove subj function? I see no practical usage for it in real applications. Do you? -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 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. What I can say for sure is that this is not a reason to delay beta1. 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 somehow - they were going to drop CS support. But ee are not goint to do it . Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 is now. Are you sure that gain from this trade-off will be big enough? -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 ticket would not be necessary as the feature didn't appeared in any alpha/beta release yet. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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_transaction_cn(T2) from rdb$database; In Super C1 returns the commit number. In Classic it returns NULL. Yes, this is because C1 see no new Next value and consider T2 as not existing. We could refresh TIP Cache in C1 but it looks as overkill in this case. That difference is not documented. README.builtin_functions.txt: --- Summary, numbers returned by RDB$GET_TRANSACTION_CN could have values below: ... NULL - given transaction number is NULL or greater than database Next Transaction --- Considering that (and not), was is the usefulness of RDB$GET_TRANSACTION_CN? It is completely useless, if you wish to say it ;) 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. Regards, Vlad Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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; >> >> In Super C1 returns the commit number. In Classic it returns NULL. > > Yes, this is because C1 see no new Next value and consider T2 as not > existing. > We could refresh TIP Cache in C1 but it looks as overkill in this case. > That difference is not documented. Considering that (and not), was is the usefulness of RDB$GET_TRANSACTION_CN? Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 NULL. Yes, this is because C1 see no new Next value and consider T2 as not existing. We could refresh TIP Cache in C1 but it looks as overkill in this case. Regards, Vlad Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] RDB$GET_TRANSACTION_CN works different in Super and Classic
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 NULL. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
