12.10.2021 13:57, Kjell Rilbe wrote:
Den 2021-10-12 kl. 08:09, skrev Roman Simakov:
пн, 11 окт. 2021 г. в 23:03, Vlad Khorsun <hv...@optima.com.ua
<mailto:hv...@optima.com.ua>>:
11.10.2021 21:23, Roman Simakov wrote:
> пн, 11 окт. 2021 г. в 18:42, Vlad Khorsun <hv...@optima.com.ua
<mailto:hv...@optima.com.ua> <mailto:hv...@optima.com.ua
<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 (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. Actually we took a look at Oracle syntax.
The fact is that DEFAULT means different things. For example,
> DEFAULT tablespace for indices is the tablespace of its table.
That's why DEFAULT is not such an obvious name as we want it to be.
This is matter of documentation, IMHO. BTW, why you don't like
ORACLE's way ?
It looks logical for me. If you want to avoid ambiguity we could
introduce
special syntax for the table's sub-objects (blob fields, indices,
constraints),
say use keyword TABLE or PARENT as tablespace name, for ex:
CREATE INDEX … AT TABLESPACE {<TS NAME> | DEFAULT | TABLE}, or
more natural
CREATE INDEX … AT DEFAULT | TABLE TABLESPACE
CREATE INDEX … AT TABLESPACE <TS NAME>
I had such an idea but didn't want to make up our own way.
If we go Oracle way and use DEFAULT we won't be able to move index data to the main database for indices for a table at;) a
tablespace. I.e. we can move either to a named tablespace or to a default (table's) tablespace.
It seems Oracle uses the name SYSTEM for the main database. Do you like it? Anyway the main database tablespace has to have a
name. The question is what name?
MAIN
PRIMARY
SYSTEM
DATABASE TABLESPACE
DATABASE
but definitely it could not be DEFAULT because DEFAULT meaning depends on the
context.
I think PRIMARY is good because it's already a reserved word and has an
appropriate meaning.
Ok, seems we have wide agreement on it.
// let me use AT until we agreed to use IN ;)
I'd like to get an answer from native speakers, but I think it's like a
database or file (in a database, in a file).
I'm not a native speaker but I consider myself to be pretty good at English,
and I'm pretty sure IN is the best word here.
Let it be IN then, thanks.
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
