ha_innodb.h:

  Revert the previous patch: MySQL would not allow creation of VARCHAR columns whose total max length is > 8000 bytes, though InnoDB can easily store them as trailing spaces are removed
parent 79f18d5b
...@@ -111,9 +111,7 @@ class ha_innobase: public handler ...@@ -111,9 +111,7 @@ class ha_innobase: public handler
return (HA_READ_NEXT | HA_READ_PREV | HA_READ_ORDER | return (HA_READ_NEXT | HA_READ_PREV | HA_READ_ORDER |
HA_KEY_READ_ONLY); HA_KEY_READ_ONLY);
} }
/* max_record_.. should be slightly less uint max_record_length() const { return HA_MAX_REC_LENGTH; }
than 1/2 UNIV_PAGE_SIZE */
uint max_record_length() const { return 8000; }
uint max_keys() const { return MAX_KEY; } uint max_keys() const { return MAX_KEY; }
uint max_key_parts() const { return MAX_REF_PARTS; } uint max_key_parts() const { return MAX_REF_PARTS; }
/* An InnoDB page must store >= 2 keys; /* An InnoDB page must store >= 2 keys;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment