11.10.2021 22:22, Lucas Schatz wrote:
Just to clarify, the use of tablespace will be optional, right?
Sure.
Dmitry
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
11.10.2021 21:23, Roman Simakov wrote:
пн, 11 окт. 2021 г. в 18:42, Vlad Khorsun mailto:hv...@optima.com.ua>>:
11.10.2021 15:17, Roman Simakov wrote:
> SYNTAX
> ===
>
> Note: *MAIN* - is a name of the basic database file.
Please, use *DEFAULT* for default
Roman Simakov wrote 11.10.2021 20:23:
> pag_header in every tablespace is reserved and may be replaced by a
> new page type.
You mean page zero, which is currently always pag_header. I see no
reason
to change this, so far. Header page uses to describe properties of
11.10.2021 19:24, Dmitry Yemanov wrote:
11.10.2021 18:41, Vlad Khorsun wrote:
2. *ALTER TABLESPACE FILE '/path/to/file'*
In DDL, ALTER usually combined with ADD | SET | DROP, so let follow this
convention. I.e. ALTER TABLESPACE SET FILE '/path/to/file'
I'm not so sure about
Just to clarify, the use of tablespace will be optional, right?
Anyway it would be a great improvement to Fb!
Thanks!
On Wed, Oct 6, 2021 at 12:33 PM Roman Simakov
wrote:
> Hello, team!
>
> As you might know Red Soft has implemented Tablespace support for
> RedDatabase 4 which is based on
Roman Simakov wrote 11.10.2021 20:23:
> Note: *MAIN* - is a name of the basic database file.
Please, use *DEFAULT* for default (main) tablespace at "main" database
file.
It is much more consistent with SQL and allows to avoid new unnecessary
keyword.
I'd be happy to agree.
>
>
> >Two ID's is reserved for DEFAULT and TEMPORARY tablespaces, correct ?
> > I would reserve some more ID's for future system usage. I don't see it as
> > limitation for end users.
>
> For regular tablespaces (created explicitly) - sure. But if we think
> about automatically created
пн, 11 окт. 2021 г. в 18:42, Vlad Khorsun :
> 11.10.2021 15:17, Roman Simakov wrote:
> > SYNTAX
> > ===
> >
> > Note: *MAIN* - is a name of the basic database file.
>
>Please, use *DEFAULT* for default (main) tablespace at "main" database
> file.
> It is much more consistent with SQL and
Dmitry Yemanov wrote 11.10.2021 18:24:
It's possible to create up to 253 tablespaces.
Two ID's is reserved for DEFAULT and TEMPORARY tablespaces, correct ?
I would reserve some more ID's for future system usage. I don't see it as
limitation for end users.
For regular tablespaces (created
11.10.2021 18:11, Dimitry Sibiryakov wrote:
In which case charset received by IReplTransaction::executeSqlIntl()
can be different from charset of attachment received by
IReplicatedSession::init()?
Ideally, never.
I can imagine only the case of cascade replication when the Applier
hacks
11.10.2021 18:41, Vlad Khorsun wrote:
2. *ALTER TABLESPACE FILE '/path/to/file'*
In DDL, ALTER usually combined with ADD | SET | DROP, so let follow this
convention. I.e. ALTER TABLESPACE SET FILE '/path/to/file'
I'm not so sure about "usually", e.g. ALTER INDEX INACTIVE, ALTER DOMAIN
11.10.2021 15:17, Roman Simakov wrote:
Here is the second version of the proposal. It's taken into account all agreements we made during discussion and we'll do it in this
way if there are no objections.
PROPOSAL==
GOALS
==
1) Extend the current limits
Hello All.
In which case charset received by IReplTransaction::executeSqlIntl() can be
different from charset of attachment received by IReplicatedSession::init()?
I can imagine only the case of cascade replication when the Applier hacks
replicator's connection charset.
--
WBR, SD.
On 11/10/2021 09:17, Roman Simakov wrote:
>
> nbackup support is postponed.
What do you mean?
Both features are supposed to be more used by big databases, so they
must work together.
Adriano
Firebird-Devel mailing list, web interface at
Roman Simakov wrote 11.10.2021 15:23:
Cannot be tablespace identification loaded from RDB$INDEXES?
Adding it into irp will increase size of irt_repeat by 1/3 decreasing limit
of indexes per table, no?
I'm sure the answer is the same as why the root page cannot be loaded
from RDB$INDEXES
пн, 11 окт. 2021 г. в 16:14, Dimitry Sibiryakov :
>
> Roman Simakov wrote 11.10.2021 14:52:
> >>> Add page space id to page number in ods.h:index_root_page.
> >>> pag_root is located in the tablespace where a table is located
> >> Why is this difference? What does prevent you from putting irp
Roman Simakov wrote 11.10.2021 14:52:
Add page space id to page number in ods.h:index_root_page.
pag_root is located in the tablespace where a table is located
Why is this difference? What does prevent you from putting irp into the
tablespace where index is located?
IRP describes every
пн, 11 окт. 2021 г. в 15:27, Dimitry Sibiryakov :
>
> Roman Simakov wrote 11.10.2021 14:17:
> > FIELD TYPE CONSTRAINT ... USING INDEX ... TABLESPACE { | MAIN} --
> > field constraint tablespace
>
>What's the point of using "MAIN" here? Whole TABLESPACE clause cannot be
> omitted?
>
> > Add
Dimitry Sibiryakov wrote 11.10.2021 14:26:
What's the point of using "MAIN" here?
Nevemind, I've found the answer.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Roman Simakov wrote 11.10.2021 14:17:
FIELD TYPE CONSTRAINT ... USING INDEX ... TABLESPACE { | MAIN} --
field constraint tablespace
What's the point of using "MAIN" here? Whole TABLESPACE clause cannot be
omitted?
Add page space id to page number in ods.h:index_root_page.
pag_root is
Here is the second version of the proposal. It's taken into account all
agreements we made during discussion and we'll do it in this way if there
are no objections.
PROPOSAL==
GOALS
==
1) Extend the current limits on database size
2) Keep non active parts
Den 2021-10-07 kl. 10:56, skrev Molnár Attila:
"Tablespaces has meaning for large databases only that don't fit into single storage
(terrabytes)."
That is not true. It has meaning whatever the programmers meant to use it. It
might not be about read performance, but e.g. logical data
On 11-10-2021 07:43, Kovalenko Dmitry wrote:
The question is whether result of negation should keep the type of
source or can it be expanded if needed.
Then it would need to expand for all types.
And what would be an -INT128?
Result type must be same as result of expression
23 matches
Mail list logo
