Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-740

In MySQL use LONGBLOB, MEDIUMBLOB etc.. when needed, cause BLOB only holds 64kb of data.


    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.2.0, 1.2.1, 1.2.2, 1.3.0, 2.0.0-M3, 2.0.0-beta, 2.0.0-beta2
    • Fix Version/s: 1.3.0, 2.0.0-beta3
    • Component/s: sql
    • Labels:
    • Patch Info:
      Patch Available


      When a column is annotated as a BLOB of using @Persistent to use streaming blobs, and the underlying database is MySQL, OpenJPA will create a column of type BLOB. Unfortunately, in MySQL a BLOB column can hold a (vary) limited amount of data, while (especially when using streaming blobs) the user would probably expect it to hold a large amount of data.

      Also adding the @Column annotation and specifying a size bigger than what a BLOB column in MySQL can hold, OpenJPA still creates only a BLOB column.

      I think OpenJPA should be able to create the proper column type depending on the @Column annotation if present, or otherwise default at least to a MEDIUMBLOB to preserve cross-database compatibility as expected.

      The simplest patch i can think of is setting blobTypeName="MEDIUMBLOB" in the MySQLDictionary constructor.

      Otherwise, overriding the getTypeName to properly parse the length and return the correct BLOB/TEXT type for mysql.


        1. OPENJPA-740-trunk.patch
          2 kB
          Donald Woods
        2. OPENJPA-740-mysqlblob.patch
          1 kB
          Simone Gianni
        3. OPENJPA-740-13x.patch
          2 kB
          Donald Woods

          Issue Links



              • Assignee:
                drwoods Donald Woods
                s.gianni Simone Gianni
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: