[MCOL-491] Change the data range of Varchar and Varbinary Created: 2016-12-29 Updated: 2023-07-25 Resolved: 2023-07-02 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Zeng Chun | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | Compatibility | ||
| Issue Links: |
|
||||||||||||||||
| Epic Link: | ColumnStore Compatibility Improvements | ||||||||||||||||
| Sprint: | 2021-7 | ||||||||||||||||
| Description |
|
Keep the same definition for character or binary types between MariaDB ColumnStore and MariaDB. Thanks for your great support. MariaDB ColumnStore:
MariaDB:
|
| Comments |
| Comment by David Hall (Inactive) [ 2021-04-19 ] |
|
The charset is correct. That is, varchar(2000) with charset utf8mb4, will reserve 2000 utf8mb4 chacracters, not bytes as it used to be. This was corrected by However, the 8000 byte limit is still in place. It may be a simple case of changing the edit for length code. |
| Comment by David Hall (Inactive) [ 2021-04-27 ] |
|
When the maximum of 8000 is relaxed, inserted strings start showing the same symptoms reported in |
| Comment by Todd Stoffel (Inactive) [ 2023-07-02 ] |
|
The "create date" on this ticket is pre-convergence with MariaDB server. If the issue still exists in a modern version of the engine/plugin please submit a new ticket. |