On 17-2-2019 18:36, liviuslivius wrote:
test message, because i have send two emails 16.02.2019 23:12
and 16.02.2019 23:27
but i still do see them on the group
I have them in my mailbox now, it looks like they were stuck for almost
a day within SourceForge:
Received: from [127.0.0.1]
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
RDB$GET_TRANSACTION_CN works different in Super and Classic
---
Key: CORE-6003
URL: http://tracker.firebirdsql.org/browse/CORE-6003
Project: Firebird Core
Issue Type: Improvement
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
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
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
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
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
On 2/18/19 2:21 PM, Adriano dos Santos Fernandes wrote:
On 16/02/2019 12:57, Mark Rotteveel wrote:
BTW: similar arguments could be made for the SET DECFLOAT options, but
I don't have a need there.
The similar SET DECFLOAT wasn't it, so TIME ZONE didn't had too.
That backward compatibility
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
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
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
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
On 16/02/2019 12:57, Mark Rotteveel wrote:
>
> BTW: similar arguments could be made for the SET DECFLOAT options, but
> I don't have a need there.
>
The similar SET DECFLOAT wasn't it, so TIME ZONE didn't had too.
Adriano
Firebird-Devel mailing list, web interface at
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;
>>
Yes. Always on all databases (~500 pieces on that server).
(Filesystem is ext3.)
András
-Original Message-
From: Alex Peshkoff via Firebird-devel
Sent: Monday, February 18, 2019 10:45 AM
To: firebird-devel@lists.sourceforge.net
Cc: Alex Peshkoff
Subject: Re: [Firebird-devel]
On 2/17/19 10:35 AM, Omacht András wrote:
Dear Developers,
https://wiki.postgresql.org/wiki/Fsync_Errors
Firebird can be also involved in the problem?
Perodically we have corrupted databases on linux (85% wrong page
type). And this cannot be reproduced for ages. Currently we are
running FB
On 2019-02-18 09:48, Alex Peshkoff via Firebird-devel wrote:
Guys, you are mixing DPB & SPB. In crazy designed SPB one really can't
use unknown for server items - server does not know how to skip
unknown iten and proceed to next. DPB (both v1 & v2) has absolutely
regular structure, one can
On 2019-02-18 01:24, Adriano dos Santos Fernandes wrote:
On 17/02/2019 08:33, Mark Rotteveel wrote:
It would be helpful if Firebird already had an explicit default value
(as then I can just document that, and I don't need to have logic to
treat a Jaybird specific value as 'don't set').
I
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
On 2/16/19 6:59 PM, Mark Rotteveel wrote:
On 16-2-2019 16:04, Dimitry Sibiryakov wrote:
16.02.2019 15:57, Mark Rotteveel wrote:
I was wondering if it was considered to also set these options
through the DPB. Especially for time zone support, I'm currently
considering not supporting this for
23 matches
Mail list logo
