From 0e788db804c60e15e3f2a8d614399e7774b44379 Mon Sep 17 00:00:00 2001 From: Ganlin Zhao <36554565+glzhao89@users.noreply.github.com> Date: Wed, 22 Dec 2021 13:16:56 +0800 Subject: [PATCH] =?UTF-8?q?[TD-12407]:=20Description=20of=20boundarie?= =?UTF-8?q?s=20of=20integer/floating=20number=E2=80=A6?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- documentation20/en/12.taos-sql/docs.md | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation20/en/12.taos-sql/docs.md b/documentation20/en/12.taos-sql/docs.md index 8533f92a3b..455b3fa363 100644 --- a/documentation20/en/12.taos-sql/docs.md +++ b/documentation20/en/12.taos-sql/docs.md @@ -60,6 +60,7 @@ In TDengine, the following 10 data types can be used in data model of an ordinar 1. TDengine is case-insensitive to English characters in SQL statements and automatically converts them to lowercase for execution. Therefore, the user's case-sensitive strings and passwords need to be enclosed in single quotation marks. 2. Avoid using BINARY type to save non-ASCII type strings, which will easily lead to errors such as garbled data. The correct way is to use NCHAR type to save Chinese characters. +3. The numerical values in SQL statements are treated as floating or integer numbers, depends on if the value contains decimal point or is in scientific notation format. E.g., 9999999999999999999 is overflow as the number is greater than the largest integer number. However, 9999999999999999999.0 is treated as a valid floating number. ## Database Management -- GitLab