Edgewall Software
Modify

Opened 10 years ago

Last modified 5 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:

Description

I success to work with MySQL cluster on Windows(x64). But some issues remain.

  1. With NDB engine, TEXT(BLOB) column cannot be used as PRIMARY KEY. So such columns will be used as VARCHAR.
  2. 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 Christian Boos, 10 years ago

Milestone: 2.0

NDB engine is not yet supported.

comment:2 by Christian Boos, 9 years ago

Milestone: 2.0unscheduled

Milestone 2.0 deleted

comment:3 by Thijs Triemstra, 9 years ago

Cc: Thijs Triemstra added
Severity: trivialminor

I've seen a patch for this somewhere, and it also might be fixed by now..

in reply to:  3 comment:4 by Thijs Triemstra, 9 years ago

Summary: On MySQL cluster, use VARCHAR instead of TEXTIssue 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 V.E.O, 7 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 Jun Omae, 5 years ago

Summary: Issue with MySQL: Maximum ROW size for NDB engine is 8052BLOB column can't be used in PRIMARY KEY and maximum ROW size is 8052 on NDB engine

#11747 was closed as a duplicate.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.