IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-1824

MySQL silently truncates text fields to 64kb

      We use the TEXT datatype for large character fields, but this only holds a maximum of 64kb of data, or 65535 non-multibyte characters (when multibyte characters are used, this could be as little as 21845 characters).

      MySQL accepts any string and silently truncates it when storing.

      Solution is to move to larger datatypes such as MEDIUMTEXT (holds max 2^24 = 16,777,215 bytes) or LONGTEXT (2^32 = 4,294,967,295 or 4GB).

      It's important to investigate the effects this may have on our full text comment search.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Crucible'
            1. Crucible
            2. CRUC-1824

            MySQL silently truncates text fields to 64kb

                We use the TEXT datatype for large character fields, but this only holds a maximum of 64kb of data, or 65535 non-multibyte characters (when multibyte characters are used, this could be as little as 21845 characters).

                MySQL accepts any string and silently truncates it when storing.

                Solution is to move to larger datatypes such as MEDIUMTEXT (holds max 2^24 = 16,777,215 bytes) or LONGTEXT (2^32 = 4,294,967,295 or 4GB).

                It's important to investigate the effects this may have on our full text comment search.

                        evzijst Erik van Zijst (Inactive)
                        evzijst Erik van Zijst (Inactive)
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Estimated:
                            Original Estimate - Not Specified
                            Not Specified
                            Remaining:
                            Remaining Estimate - 0h
                            0h
                            Logged:
                            Time Spent - 8h 10m
                            8h 10m

                              evzijst Erik van Zijst (Inactive)
                              evzijst Erik van Zijst (Inactive)
                              Affected customers:
                              0 This affects my team
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved:

                                  Estimated:
                                  Original Estimate - Not Specified
                                  Not Specified
                                  Remaining:
                                  Remaining Estimate - 0h
                                  0h
                                  Logged:
                                  Time Spent - 8h 10m
                                  8h 10m