Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
Under terms of MDEV-274 we added the INET6 data type, to store IPv6 addresses as 16-byte binary strings.
Let's also add a data type to store IPv4 addresses, as 4-byte binary strings.
The new data type name will be INET4.
Under terms of this task, INET4 and INET6 won't support mutual explicit or implicit CAST. That will be done separately when needed.
But INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so later INET4 and INET6 "know" each other, to implement mutual cast.
Attachments
Issue Links
- causes
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
MDEV-29920 INET4 data type is not documented
-
- Closed
-
Activity
| Description |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so INET4 and INET6 "know" each other: - They should support explicit CAST between each other - INET6 should be a super type for INET4. {code:sql} SELECT COALEACE(inet4_expr,inet6_expr) {code} will implicitly cast inet4_expr to INET6 and return a result of the INET6 data type. {code:sql} SELECT inet4_expr=inet6_expr) {code} will implicitly cast inet4_expr to INET6, then compare in INET6 format. - They should possibly support implicit CAST between each other in some other cases. The exact list is to be defined. |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so INET4 and INET6 "know" each other: - They should support explicit CAST between each other - INET6 should be a super type for INET4. {code:sql} SELECT COALEACE(inet4_expr,inet6_expr) {code} will implicitly cast inet4_expr to INET6 and return a result of the INET6 data type. {code:sql} SELECT inet4_expr=inet6_expr) {code} will implicitly cast inet4_expr to INET6, then compare in INET6 format. - They should possibly support implicit CAST between each other in some other cases. The exact list is to be defined. |
| Rank | Ranked higher |
| Assignee | Alexander Barkov [ bar ] | Oleksandr Byelkin [ sanja ] |
| Fix Version/s | 10.7 [ 24805 ] | |
| Fix Version/s | 10.6 [ 24028 ] |
| Fix Version/s | 10.8 [ 26121 ] | |
| Fix Version/s | 10.7 [ 24805 ] |
| Assignee | Oleksandr Byelkin [ sanja ] | Alexander Barkov [ bar ] |
| Workflow | MariaDB v3 [ 111695 ] | MariaDB v4 [ 131338 ] |
| Fix Version/s | 10.9 [ 26905 ] | |
| Fix Version/s | 10.8 [ 26121 ] |
| Fix Version/s | 10.10 [ 27530 ] | |
| Fix Version/s | 10.9 [ 26905 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Description |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so INET4 and INET6 "know" each other: - They should support explicit CAST between each other - INET6 should be a super type for INET4. {code:sql} SELECT COALEACE(inet4_expr,inet6_expr) {code} will implicitly cast inet4_expr to INET6 and return a result of the INET6 data type. {code:sql} SELECT inet4_expr=inet6_expr) {code} will implicitly cast inet4_expr to INET6, then compare in INET6 format. - They should possibly support implicit CAST between each other in some other cases. The exact list is to be defined. |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. Under terms of this task, INET4 and INET6 won't support mutual explicit or implicit CAST. That will be done separately when needed. But INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so later INET4 and INET6 "know" each other. |
| Description |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. Under terms of this task, INET4 and INET6 won't support mutual explicit or implicit CAST. That will be done separately when needed. But INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so later INET4 and INET6 "know" each other. |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. Under terms of this task, INET4 and INET6 won't support mutual explicit or implicit CAST. That will be done separately when needed. But INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so later INET4 and INET6 "know" each other, to implement mutual cast. |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Testing [ 10301 ] |
| Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
| Assignee | Alexander Barkov [ bar ] | Sergei Golubchik [ serg ] |
| Status | Stalled [ 10000 ] | In Review [ 10002 ] |
| Assignee | Sergei Golubchik [ serg ] | Alexander Barkov [ bar ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Status | Stalled [ 10000 ] | In Testing [ 10301 ] |
| Assignee | Alexander Barkov [ bar ] | Elena Stepanova [ elenst ] |
| Assignee | Elena Stepanova [ elenst ] | Alice Sherepa [ alice ] |
| Assignee | Alice Sherepa [ alice ] | Alexander Barkov [ bar ] |
| Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.10.0 [ 27912 ] | |
| Fix Version/s | 10.10 [ 27530 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Summary | The INET4 data type | INET4 data type |
| Description |
Under terms of Let's also add a data type to store IPv4 addresses, as 4-byte binary strings. The new data type name will be INET4. Under terms of this task, INET4 and INET6 won't support mutual explicit or implicit CAST. That will be done separately when needed. But INET4 should be implemented in the same directory with INET6: plugin/type_inet/, so later INET4 and INET6 "know" each other, to implement mutual cast. |
Under terms of Let's also add a data type to store IPv4 addresses, as 4\-byte binary strings. The new data type name will be INET4. Under terms of this task, INET4 and INET6 won't support mutual explicit or implicit CAST. That will be done separately when needed. But INET4 should be implemented in the same directory with INET6: plugin/type\_inet/, so later INET4 and INET6 "know" each other, to implement mutual cast. |
| Link |
This issue causes |
| Labels | Preview_10.10 |
| Link |
This issue relates to |