Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3.0, 2.0.0-beta3
    • Component/s: jdbc
    • Labels:
      None

      Description

      The MySQLDictionary currently supports only TYPE innodb. There is a skeleton for support of this element but there is no way to change it from the default.

      Also, according to the MySQL documentation http://dev.mysql.com/doc/refman/5.1/en/create-table.html TYPE is deprecated. The recommended (and supported) keyword is ENGINE.

      "Since MySQL 5.1.8, it produces a warning. It will be removed in a future MySQL release. You should not use TYPE in any new applications, and you should immediately begin conversion of existing applications to use ENGINE instead."

      I propose to change TYPE to ENGINE, and to provide a way for the user to specify which engine to use.

      I need some feedback on this: A property, mysql.engine, with a default of innodb (for compatibility) can be specified by the user in order to create tables using any of the supported engines. Can the property be put onto the command line? Can the property be added to persistence.xml? Can the property be added to the maven profile properties?

      1. openjpa-1530.patch
        3 kB
        Craig L Russell

        Activity

        Craig L Russell created issue -
        Craig L Russell made changes -
        Field Original Value New Value
        Summary Support specification of storage engine type for MySQL MySQL storage engine support
        Description The MySQLDictionary currently supports only TYPE innodb. There is a skeleton for support of this element but there is no way to change it from the default.

        Also, according to the MySQL documentation, TYPE is deprecated. The recommended (and supported) keyword is ENGINE.

        I propose to change TYPE to ENGINE, and to provide a way for the user to specify which engine to use.

        Also, a property, mysql.engine, with a default of innodb (for compatibility) can be specified by the user in order to create tables using any of the supported engines.
        The MySQLDictionary currently supports only TYPE innodb. There is a skeleton for support of this element but there is no way to change it from the default.

        Also, according to the MySQL documentation http://dev.mysql.com/doc/refman/5.1/en/create-table.html TYPE is deprecated. The recommended (and supported) keyword is ENGINE.

        "Since MySQL 5.1.8, it produces a warning. It will be removed in a future MySQL release. You should not use TYPE in any new applications, and you should immediately begin conversion of existing applications to use ENGINE instead."

        I propose to change TYPE to ENGINE, and to provide a way for the user to specify which engine to use.

        I need some feedback on this: A property, mysql.engine, with a default of innodb (for compatibility) can be specified by the user in order to create tables using any of the supported engines. Can the property be put onto the command line? Can the property be added to persistence.xml? Can the property be added to the maven profile properties?
        Craig L Russell made changes -
        Attachment openjpa-1530.patch [ 12437066 ]
        Craig L Russell made changes -
        Fix Version/s 2.0.0 [ 12314019 ]
        Fix Version/s 1.3.0 [ 12313326 ]
        Craig L Russell made changes -
        Fix Version/s 1.3.0 [ 12313326 ]
        Craig L Russell made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Craig L Russell made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Donald Woods made changes -
        Fix Version/s 2.0.0-beta3 [ 12314857 ]
        Fix Version/s 2.0.0 [ 12314019 ]

          People

          • Assignee:
            Craig L Russell
            Reporter:
            Craig L Russell
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development