Opened 15 years ago
Last modified 10 years ago
#8567 new defect
BLOB column can't be used in PRIMARY KEY and maximum ROW size is 8052 on NDB engine
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | unscheduled |
| Component: | database backend | Version: | 0.11.5 |
| Severity: | minor | Keywords: | mysql |
| Cc: | Thijs Triemstra | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I success to work with MySQL cluster on Windows(x64). But some issues remain.
- With NDB engine, TEXT(BLOB) column cannot be used as PRIMARY KEY. So such columns will be used as VARCHAR.
- Maximum ROW size for NDB engine is 8052. So, long wiki, tickets and etc are cut off by limit.
Attachments (0)
Change History (6)
comment:1 by , 14 years ago
| Milestone: | → 2.0 |
|---|
follow-up: 4 comment:3 by , 13 years ago
| Cc: | added |
|---|---|
| Severity: | trivial → minor |
I've seen a patch for this somewhere, and it also might be fixed by now..
comment:4 by , 13 years ago
| Summary: | On MySQL cluster, use VARCHAR instead of TEXT → Issue with MySQL: Maximum ROW size for NDB engine is 8052 |
|---|
Replying to thijstriemstra:
I've seen a patch for this somewhere, and it also might be fixed by now..
I was referring to the VARCHAR issue, so updating the ticket title.
comment:5 by , 11 years ago
Migrate to cluster is definitely not a good idea. Change from text to varchar, we cannot forbid user for inputting large data and truncate them without notification.
And the most concern is during my several months' running on cluster, custom fields query or any query include join or cross table exhausts user's patience, even exceeds gunicorn's default timeout.
comment:6 by , 10 years ago
| Summary: | Issue with MySQL: Maximum ROW size for NDB engine is 8052 → BLOB column can't be used in PRIMARY KEY and maximum ROW size is 8052 on NDB engine |
|---|
#11747 was closed as a duplicate.
NDB engine is not yet supported.