[glotpress-updates] [GlotPress] #349: Glotpress install SQL ERROR!

[GlotPress]

#349: Glotpress install SQL ERROR!
-----------------------+-----------------
  Reporter:  KardiWeb  |      Owner:
      Type:  defect    |     Status:  new
  Priority:  critical  |  Milestone:  1.0
 Component:  Database  |    Version:  0.1
Resolution:            |   Keywords:
-----------------------+-----------------

Comment (by pento):

 We've had a [https://core.trac.wordpress.org/ticket/21212 similar problem
 in Core].

 Given that the larger index options in MySQL aren't really practical (or
 backwards compatible), I would suggest decreasing the size of the prefix
 on each column. To save on future headaches, I'd recommend making this
 change with `utf8mb4` in mind, rather than `utf8`.

 With a 1000 byte limit, and up to 4 bytes per character in `utf8mb4`, that
 leaves:

 `floor( 1000 / 4 / 3 ) = 83` characters per column.

 So, the index definition should be:

 {{{
 KEY `singular_plural_context` (`singular`(83), `plural`(83),
 `context`(83))
 }}}

 From a quick read through `schema.php`, it looks like this is the only
 index that would need to be changed to support `utf8`, though there are a
 few that would need to change to support `utf8mb4`.

--
Ticket URL: <https://glotpress.trac.wordpress.org/ticket/349#comment:4>
GlotPress <https://glotpress.trac.wordpress.org>
Easy comin', easy goin'