testing_project/Documentation: reference/reference_sql/sql_statements_and_clauses — Russian @ Weblate: -- with all possible data types and aliases CREATE TABLE …

Translation

English

-- with all possible data types and aliases
CREATE TABLE t
(column1 BOOLEAN, column2 BOOL,
column3 INT PRIMARY KEY, column4 INTEGER,
column5 DOUBLE,
column6 NUMBER,
column7 STRING, column8 STRING COLLATE "unicode",
column9 TEXT, columna TEXT COLLATE "unicode_sv_s1",
columnb VARCHAR(0), columnc VARCHAR(100000) COLLATE "binary",
columnd UUID,
columne VARBINARY,
columnf SCALAR, columng SCALAR COLLATE "unicode_uk_s2",
columnh DECIMAL,
columni ARRAY,
columnj MAP,
columnk ANY);

Russian

Needs editing

Skip

	English	Russian	Actions
	CHECK (expression)
	foreign-key-clause
	explained in the :ref:`Table constraint definition for foreign keys <sql_foreign_key>` section
	DEFAULT expression
	means "if INSERT does not assign to this column then assign expression result to this column" -- if there is no DEFAULT clause then DEFAULT NULL is assumed
	If column-constraint is PRIMARY KEY, this is a shorthand for a separate :ref:`table-constraint definition <sql_table_constraint_def>`: "PRIMARY KEY (column-name)".
	If column-constraint is UNIQUE, this is a shorthand for a separate :ref:`table-constraint definition <sql_table_constraint_def>`: "UNIQUE (column-name)".
	If column-constraint is CHECK, this is a shorthand for a separate :ref:`table-constraint definition <sql_table_constraint_def>`: "CHECK (expression)".
	Columns defined with PRIMARY KEY are automatically NOT NULL.
	To enforce some restrictions that Tarantool does not enforce automatically, add CHECK clauses, like these:
	CREATE TABLE t ("smallint" INTEGER PRIMARY KEY CHECK ("smallint" <= 32767 AND "smallint" >= -32768)); CREATE TABLE t ("shorttext" STRING PRIMARY KEY CHECK (length("shorttext") <= 10));
	but this may cause inserts or updates to be slow.
	Column definition -- examples
	These are shown within :ref:`CREATE TABLE <sql_create_table>` statements. Data types may also appear in :ref:`CAST <sql_function_cast>` functions.
	-- the simple form with column-name and data-type CREATE TABLE t (column1 INTEGER ...); -- with column-name and data-type and column-constraint CREATE TABLE t (column1 STRING PRIMARY KEY ...); -- with column-name and data-type and collate-clause CREATE TABLE t (column1 SCALAR COLLATE "unicode" ...);
	-- with all possible data types and aliases CREATE TABLE t (column1 BOOLEAN, column2 BOOL, column3 INT PRIMARY KEY, column4 INTEGER, column5 DOUBLE, column6 NUMBER, column7 STRING, column8 STRING COLLATE "unicode", column9 TEXT, columna TEXT COLLATE "unicode_sv_s1", columnb VARCHAR(0), columnc VARCHAR(100000) COLLATE "binary", columnd UUID, columne VARBINARY, columnf SCALAR, columng SCALAR COLLATE "unicode_uk_s2", columnh DECIMAL, columni ARRAY, columnj MAP, columnk ANY);	-- со всеми возможными типами данных и алиасами CREATE TABLE t (column1 BOOLEAN, column2 BOOL, column3 INT PRIMARY KEY, column4 INTEGER, column5 DOUBLE, column6 NUMBER, column7 STRING, column8 STRING COLLATE "unicode", column9 TEXT, columna TEXT COLLATE "unicode_sv_s1", columnb VARCHAR(0), columnc VARCHAR(100000) COLLATE "binary", columnd UUID, columne VARBINARY, columnf SCALAR, columng SCALAR COLLATE "unicode_uk_s2", columnh DECIMAL);
	-- with all possible column constraints and a default clause CREATE TABLE t (column1 INTEGER NOT NULL, column2 INTEGER PRIMARY KEY, column3 INTEGER UNIQUE, column4 INTEGER CHECK (column3 > column2), column5 INTEGER REFERENCES t, column6 INTEGER DEFAULT NULL);
	Table constraint definition
	A table :ref:`constraint <index-constraints>` restricts the data you can add to the table. If you try to insert invalid data on a column, Tarantool throws an error.
	A table constraint has the following syntax:
	[CONSTRAINT [name]] constraint_expression constraint_expression: \| PRIMARY KEY (column_name, ...) \| UNIQUE (column_name, ...) \| CHECK (expression) \| FOREIGN KEY (column_name, ...) foreign_key_clause
	Define a constraint, which is a table element used in a CREATE TABLE statement.
	A constraint name must be an identifier that is valid according to the rules for identifiers. A constraint name must be unique within the table for a specific constraint type. For example, the CHECK and FOREIGN KEY constraints can have the same name.
	PRIMARY KEY constraints
	PRIMARY KEY constraints look like this:
	PRIMARY KEY (column_name, ...)
	There is a shorthand: specifying PRIMARY KEY in a :ref:`column definition <sql_column_def_constraint>`.
	Every table must have one and only one primary key.
	Primary-key columns are automatically ``NOT NULL``.
	Primary-key columns are automatically indexed.
	Primary-key columns are unique. That means it is illegal to have two rows with the same values for the columns specified in the constraint.

Loading…

None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

English

Russian 449 characters edited Current translation Needs editing

-- со всеми возможными типами данных и алиасами
CREATE TABLE t
(column1 BOOLEAN, column2 BOOL,
column3 INT PRIMARY KEY, column4 INTEGER,
column5 DOUBLE,
column6 NUMBER,
column7 STRING, column8 STRING COLLATE "unicode",
column9 TEXT, columna TEXT COLLATE "unicode_sv_s1",
columnb VARCHAR(0), columnc VARCHAR(100000) COLLATE "binary",
columnd UUID,
columne VARBINARY,
columnf SCALAR, columng SCALAR COLLATE "unicode_uk_s2",
columnh DECIMAL);

a year ago

Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Russian
No related strings found in the glossary.

String information

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

locale/ru/LC_MESSAGES/reference/reference_sql/sql_statements_and_clauses.po, string 125