pingcap / pingcap/tidb

`IS_IPV4_COMPAT` gives wrong result for all zero value

Open
#59,458 2 comments 0 reactions 0 assignees View on GitHub
component/expression severity/moderate sig/execution type/bug
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)

### 2. What did you expect to see? (Required)

```
mysql> SELECT IS_IPV4_COMPAT(X'00000000000000000000000000000000');
+-----------------------------------------------------+
| IS_IPV4_COMPAT(X'00000000000000000000000000000000') |
+-----------------------------------------------------+
| 0 |
+-----------------------------------------------------+
1 row in set (0.04 sec)
```

### 3. What did you see instead (Required)

```
mysql> SELECT IS_IPV4_COMPAT(X'00000000000000000000000000000000');
+-----------------------------------------------------+
| IS_IPV4_COMPAT(X'00000000000000000000000000000000') |
+-----------------------------------------------------+
| 1 |
+-----------------------------------------------------+
1 row in set (0.00 sec)
```

### 4. What is your TiDB version? (Required)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.