ClickHouse/tests/queries/0_stateless/01750_parsing_exception.sh

#!/usr/bin/env bash

CURDIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
# shellcheck source=../shell_config.sh
. "$CURDIR"/../shell_config.sh

# if it will not match, the exit code of grep will be non-zero and the test will fail
$CLICKHOUSE_CLIENT -q "SELECT toDateTime(format('{}-{}-01 00:00:00', '2021', '1'))" |& grep -F -q "Cannot parse string '2021-1-01 00:00:00' as DateTime"
Fix ParsingException::displayText() Before it was silently try-catched for messages with additional {}, and it is very easy to trigger, i.e.: SELECT toDateTime(format('{}-{}-01 00:00:00', '2021', '1')) Will print: Code: 41. DB::Exception: Received from localhost:9000. DB::Exception: Cannot parse datetime 2021-1-01 00:00:00{}: Cannot parse DateTime from String: while executing 'FUNCTION toDateTime(format('{}-{}-01 00:00:00', '2021', '1') :: 3) -> toDateTime(format('{}-{}-01 00:00:00', '2021', '1')) DateTime : 2'. 2021-03-03 20:44:51 +00:00			`#!/usr/bin/env bash`

			`CURDIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)`
			`# shellcheck source=../shell_config.sh`
			`. "$CURDIR"/../shell_config.sh`

			`# if it will not match, the exit code of grep will be non-zero and the test will fail`
Fix test 2022-08-21 23:21:32 +00:00			`$CLICKHOUSE_CLIENT -q "SELECT toDateTime(format('{}-{}-01 00:00:00', '2021', '1'))" \|& grep -F -q "Cannot parse string '2021-1-01 00:00:00' as DateTime"`