23.11.2018 23:12, Dimitry Sibiryakov wrote:
can store sequence number elsewhere (and it did until recently), but
it's more error-prone to store it inside the database itself. Header
page is an obvious choice. RDB$DATABASE is another option, but it's
also an ODS change.
Isn't a sequence e
On 23/11/2018 14:31, Dimitry Sibiryakov wrote:
>
>>> Do we need timezone there at all?
>>
>> Yes. I we do not want to have half-done TZ support.
>
> Isn't UTC better there?
>
It's an option. But we lose TZ from who created it.
It would be ok for me if others agree.
Adriano
Firebird-
24.11.2018 0:32, Dimitry Sibiryakov пишет:
23.11.2018 21:36, Vlad Khorsun wrote:
...recently invented SCN
Recently ? What do you speak about ?
"When any transaction is committed, database Commit Number is incremented and
its value is associated with this transaction".
Commit N
23.11.2018 21:36, Vlad Khorsun wrote:
...recently invented SCN
Recently ? What do you speak about ?
"When any transaction is committed, database Commit Number is incremented and
its value is associated with this transaction".
IIRC, the journal counter does exactly the same.
--
WB
23.11.2018 22:12, Dimitry Sibiryakov wrote:
...recently invented SCN
Recently ? What do you speak about ?
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
23.11.2018 20:43, Dmitry Yemanov wrote:
can store sequence number elsewhere (and it did until recently), but it's more error-prone
to store it inside the database itself. Header page is an obvious choice. RDB$DATABASE is
another option, but it's also an ODS change.
Isn't a sequence even more
23.11.2018 22:32, Dimitry Sibiryakov wrote:
AFAIU, journal sequence is completely plugin-related thing. I
understand why your plugin wants to keep it in database, but why in header?
Is replication going to be based on plugin at all?..
Built-in replication, while implementing the same CDC int
23.11.2018 20:09, Dmitry Yemanov wrote:
(1) Database GUID and (2) journal sequence.
Both are not absolutely required but useful.
AFAIU, journal sequence is completely plugin-related thing. I understand why your
plugin wants to keep it in database, but why in header?
Is replication going
23.11.2018 20:12, Dimitry Sibiryakov wrote:
I also have a couple of header page changes in my replication branch
Wow... What they are?
(1) Database GUID and (2) journal sequence.
Both are not absolutely required but useful.
Dmitry
Firebird-Devel mailing list, web interface at
https
23.11.2018 17:50, Dmitry Yemanov wrote:
I also have a couple of header page changes in my replication branch
Wow... What they are?
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
23.11.2018 18:07, Alex Peshkoff via Firebird-devel wrote:
But if others do think that accessing such databases is possible may be we should better
set current minor to 1 and also set ODS_RELEASED = 1 ? This should help efficiently avoid
opening alpha-created databases by stable release.
Nop
On 11/23/18 7:50 PM, Dmitry Yemanov wrote:
23.11.2018 17:53, Adriano dos Santos Fernandes wrote:
Does anyone see any problem in extending (in time zones branch)
hdr_creation_date to include the time zone?
Already existing (created in Alpha) ODS13 databases will be
inaccessible (or FB will cr
23.11.2018 17:53, Adriano dos Santos Fernandes wrote:
Does anyone see any problem in extending (in time zones branch)
hdr_creation_date to include the time zone?
Already existing (created in Alpha) ODS13 databases will be inaccessible
(or FB will crash while accessing them). Probably not an a
23.11.2018 17:58, Alex Peshkoff via Firebird-devel wrote:
Before beta release - absolutely no problem. BTW - when are you going to
merge that branch?
I was going to merge it this weekend.
Dmitry
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/f
23.11.2018 16:32, Alex Peshkoff via Firebird-devel wrote:
Older gstat and third-party tools won't be able to handle it correctly.
What gstat version do you talk about?
Particularly Avalerion one. It does not support full functionality for unknown ODS, but
at least it try to dump fixed pa
On 11/23/18 5:59 PM, Dimitry Sibiryakov wrote:
23.11.2018 15:53, Adriano dos Santos Fernandes wrote:
Does anyone see any problem in extending (in time zones branch)
hdr_creation_date to include the time zone?
Older gstat and third-party tools won't be able to handle it correctly.
What gsta
On 11/23/18 5:58 PM, Adriano dos Santos Fernandes wrote:
Hi!
Isn't this utility obsolete? Could it be removed in master?
I think yes - in a case we really need that ancient code (do not know
why but if...) it can be found in old branches.
Firebird-Devel mailing list, web interface at
h
23.11.2018 15:53, Adriano dos Santos Fernandes wrote:
Does anyone see any problem in extending (in time zones branch)
hdr_creation_date to include the time zone?
Older gstat and third-party tools won't be able to handle it correctly.
Do we need timezone there at all? If yes, it is better to
Hi!
Isn't this utility obsolete? Could it be removed in master?
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 11/23/18 5:53 PM, Adriano dos Santos Fernandes wrote:
Hi!
Does anyone see any problem in extending (in time zones branch)
hdr_creation_date to include the time zone?
Before beta release - absolutely no problem. BTW - when are you going to
merge that branch?
Firebird-Devel mailing list,
Hi!
Does anyone see any problem in extending (in time zones branch)
hdr_creation_date to include the time zone?
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
21 matches
Mail list logo
