Skip to content

Fix wording #3623

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 17, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/reference/reference_sql/sql_user_guide.rst
Original file line number Diff line number Diff line change
Expand Up @@ -644,7 +644,7 @@ A datetime table field can be created by using this type, which is semantically
- ['2022-01-01T00:00:00Z']
...

There is no implicit cast available from a string expression to a datetime expression (dislike convention used by majority of SQL vendors).
There is no implicit cast available from a string expression to a datetime expression (unlike convention used by majority of SQL vendors).
In such cases, you need to use explicit cast from a string value to a datetime value (see the example above).

You can subtract datetime and datetime, datetime and interval, or add datetime and interval in any order (see examples of such arithmetics in the description of the :ref:`INTERVAL type <sql_data_type_interval>`).
Expand Down Expand Up @@ -679,7 +679,7 @@ Similarly to the :ref:`DATETIME <sql_data_type_datetime>` type, you can define a
- ['2022-02-02T01:01:00Z', '+1 years, 1 months']
...

Dislike DATETIME, INTERVAL cannot be a part of an index.
Unlike DATETIME, INTERVAL cannot be a part of an index.

There is no implicit cast available for conversions to an interval from a string or any other type.
But there is explicit cast allowed from maps (see examples below).
Expand Down