Uploaded image for project: 'eXo-JCR'
  1. eXo-JCR
  2. EXOJCR-1612

Create a specific dialect to allow to use MyISAM instead of InnoDB

    Details

      Description

      MyISAM is a MySQL engine that has never been supported by eXo JCR due to its lack of transaction support and integrity check (as described in this article http://www.kavoir.com/2009/09/mysql-engines-innodb-vs-myisam-a-comparison-of-pros-and-cons.html). The purpose of this issue is to provide a specific dialect like mysql_myisam_uf8 to allow eXo JCR users to use MyISAM instead of InnoDB (the default engine used by the JCR) if in the context of their application, the performances in read accesses are more important than the consistency. However we will add a warning in the log indicating that this MySQL engine is not supported so we cannot take any responsibilities in case of inconsistency issues. In other words this dialect is for the community only so no support will be provided in case it is used by the customer.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                nfilotto Nicolas Filotto
                Reporter:
                skabashnyuk Sergey Kabashnyuk
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: