Modify ↓
Ticket #8567 (new defect)
Opened 2 years ago
Last modified 15 months ago
Issue with MySQL: Maximum ROW size for NDB engine is 8052
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | unscheduled |
| Component: | database backend | Version: | 0.11.5 |
| Severity: | minor | Keywords: | mysql |
| Cc: | thijstriemstra | ||
| Release Notes: | |||
| API 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
Change History
comment:1 Changed 2 years ago by cboos
- Milestone set to 2.0
comment:2 Changed 22 months ago by cboos
- Milestone changed from 2.0 to unscheduled
Milestone 2.0 deleted
comment:3 follow-up: ↓ 4 Changed 15 months ago by thijstriemstra
- Cc thijstriemstra added
- Severity changed from trivial to minor
I've seen a patch for this somewhere, and it also might be fixed by now..
comment:4 in reply to: ↑ 3 Changed 15 months ago by thijstriemstra
- Summary changed from On MySQL cluster, use VARCHAR instead of TEXT to 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.
Note: See
TracTickets for help on using
tickets.



NDB engine is not yet supported.