Overview

Project website www.tarantool.io/en/doc/latest
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:tarantool/doc.git
Repository branch test-weblate
Weblate repository http://weblate.tarantool.io/git/testing_project/documentation-referencereference_sqlsql-features/
File mask locale/*/LC_MESSAGES/reference/reference_sql/sql_user_guide.po
Translation file Not available
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 357 8,677 56,423
Translated 100% 357 100% 8,677 100% 56,423
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 357 100% 8,677 100% 56,423
Failing checks 6% 24 20% 1,775 22% 12,612
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 357 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

8,677
Hosted words
357
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

Although it is not a requirement of the SQL standard, implicit cast is supposed to help compatibility with other DBMSs. However, other DBMSs have different rules about what can be converted (for example they may allow assignment of ``'inf'`` but disallow comparison with ``'1e5'``). And, of course, it is not possible to be compatible with other DBMSs and at the same time support SCALAR, which other DBMSs do not have.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

For function arguments: |br| If the function description says that a parameter has a specific data type, and implicit assignment casts are allowed, then arguments which are not passed with that data type will be converted before the function is applied. |br| For example, the :ref:`LENGTH() <sql_function_length>` function expects a STRING or VARBINARY, and INTEGER can be converted to STRING, therefore LENGTH(15) will return the length of ``'15'``, that is, 2. |br| But implicit cast sometimes does NOT happen for parameters. Therefore ``ABS('5')`` will cause an error message after `Issue#4159 <https://github.com/tarantool/tarantool/issues/4159>`_ is fixed. However, :ref:`TRIM(5) <sql_function_trim>` will still be legal.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

Implicit cast does NOT happen for :ref:`GREATEST() <sql_function_greatest>` or :ref:`LEAST() <sql_function_least>`. Therefore ``LEAST('5',6)`` is 6.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

In the following examples, implicit cast does not happen for values in SCALAR columns: |br| ``DROP TABLE scalars;`` |br| ``CREATE TABLE scalars (scalar_column SCALAR PRIMARY KEY);`` |br| ``INSERT INTO scalars VALUES (11), ('2');`` |br| ``SELECT * FROM scalars WHERE scalar_column > 11; /* 0 rows. So 11 > '2'. */`` |br| ``SELECT * FROM scalars WHERE scalar_column < '2'; /* 1 row. So 11 < '2'. */`` |br| ``SELECT max(scalar_column) FROM scalars; /* 1 row: '2'. So 11 < '2'. */`` |br| ``SELECT sum(scalar_column) FROM scalars; /* 1 row: 13. So cast happened. */`` |br| These results are not affected by indexing, or by reversing the operands.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

Implicit cast does NOT happen if numerics are used in concatenation, or in LIKE. |br| Therefore ``5 || '5'`` is illegal.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

Implicit cast does happen if STRINGS are used in arithmetic. |br| Therefore ``'5' / '5' = 1``. If the cast fails, then the result is an error. |br| Therefore ``'5' / ''`` is an error.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

For assignments, due to a change in behavior starting with Tarantool :doc:`2.5.1 </release/2.5.1>`, implicit casts from strings to numerics are not legal. Therefore ``INSERT INTO t (integer_column) VALUES ('5');`` is an error.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

For comparisons, the cast is always from STRING to numeric. |br| Therefore ``1e2 = '100'`` is TRUE, and ``11 > '2'`` is TRUE. |br| If the cast fails, then the numeric is less than the STRING. |br| Therefore ``1e400 < ''`` is TRUE. |br| Exception: for BETWEEN the cast is to the data type of the first and last operands. |br| Therefore ``'66' BETWEEN 5 AND '7'`` is TRUE.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

``1 = '1' /* compare a STRING with a numeric */`` |br| ``UPDATE ... SET string_column = 1 /* assign a numeric to a STRING */``
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_user_guide — English

Special considerations may apply for casting STRINGs to/from INTEGERs/DOUBLEs/NUMBERs/UNSIGNEDs (numerics) for comparison or assignment.
a year ago
Browse all translation changes