Changeset 7997


Ignore:
Timestamp:
Aug 9, 2021, 3:32:20 PM (14 months ago)
Author:
Nicklas Nordborg
Message:

Updated documentation about MySQL support is ending.

Location:
trunk
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • trunk/config/dist/base.config

    r7822 r7997  
    3333db.queries          = /postgres-queries.xml
    3434
    35 # -----
    36 # MySQL
    37 # -----
     35# -------------------------------------
     36# MySQL (not supported since BASE 3.19)
     37# -------------------------------------
    3838# db.dialect          = org.hibernate.dialect.MySQL8Dialect
    3939# db.url              = jdbc:mysql://localhost/base2?characterEncoding=UTF-8&useCursorFetch=true&defaultFetchSize=100&useServerPrepStmts=true&sslMode=DISABLED
  • trunk/doc/src/docbook/admin/installation.xml

    r7982 r7997  
    4747
    4848    <important id="installation.upgrade.important">
    49       <title>Important information for upgrading to BASE 3.18</title>
     49      <title>Important information for upgrading to BASE 3.19</title>
    5050      <para>
    5151        This section list some important information that may or may not
    5252        apply when upgrading from the <emphasis>previous</emphasis> BASE
    53         release to the current release (eg. 3.17 to 3.18). If you are
    54         upgrading from a BASE installation that is older (3.0-3.16)
     53        release to the current release (eg. 3.18 to 3.19). If you are
     54        upgrading from a BASE installation that is older (3.0-3.17)
    5555        you should also read <xref linkend="appendix.update_warnings" />.
    5656      </para>
    5757     
    58       <bridgehead>Support for MySQL is ending in BSE 3.19</bridgehead>
     58      <bridgehead>Support for MySQL has ended</bridgehead>
    5959      <para>
    60         This is the last release of BASE that is tested with MySQL 8.0.
    61         Starting with BASE 3.19 we will only test with and support PostgreSQL.
    62         BASE may still work with MySQL after that, but we recommend that
    63         existing installations are migrated to PostgreSQL as soon as possible.
     60        BASE 3.18 was the last release that supported MySQL. Since 
     61        BASE 3.19 we are only testing and supporting PostgreSQL. BASE may still
     62        work with MySQL after that, but we recommend that existing installations
     63        are migrated to PostgreSQL as soon as possible.
    6464      </para>
    6565   
     
    272272            url="http://www.hibernate.org/">Hibernate</ulink> for
    273273            object persistence to a relational database. Hibernate
    274             supports many database engines, but so far we only work
    275             with <ulink url="http://www.postgresql.org/">PostgreSQL</ulink> (recommended)
    276             and <ulink url="http://www.mysql.com">MySQL</ulink>.
     274            supports many database engines, but at the moment we only work
     275            with <ulink url="http://www.postgresql.org/">PostgreSQL</ulink>.
     276            Support for <ulink url="http://www.mysql.com">MySQL</ulink> was ended in BASE 3.19.
    277277          </para>
    278278
     
    289289                  pre-configured for PostgreSQL so there is no need to change database
    290290                  settings in the BASE configuration files.
    291                 </para>
    292               </listitem>
    293             </varlistentry>
    294             <varlistentry>
    295               <term>MySQL (support is ending in BASE 3.19)</term>
    296               <listitem>
    297                 <para>
    298                   Support for MySQL is ending in BASE 3.19. We do not
    299                   recommend that MySQL is used for new installations.
    300                   Existing installation should migrate to PostgreSQL
    301                   as soon as possible. See <xref linkend="installation.migrate" />.
    302                   Download MySQL from
    303                   <ulink url="http://www.mysql.com/" />. You need to
    304                   be able to connect to the server over TCP, so
    305                   the <emphasis>skip-networking</emphasis> option
    306                   must <command>not</command> be used. The InnoDB
    307                   table engine is also needed, so do not disable them
    308                   (not that you would) but you may want to tune the
    309                   InnoDB behaviour before creating BASE
    310                   databases.
    311                  
    312                   You must edit your <filename>&lt;base-dir&gt;/www/WEB-INF/classes/base.config</filename>
    313                   file. Uncomment the settings for MySQL and
    314                   comment out the settings for PostgreSQL.
    315291                </para>
    316292              </listitem>
     
    375351                  template1</command> The header in the script file
    376352                  contains further information about the script.
    377                 </para>
    378               </listitem>
    379             </varlistentry>
    380             <varlistentry>
    381               <term>MySQL</term>
    382               <listitem>
    383                 <para>
    384                   Create a new database for BASE, and add a
    385                   <emphasis>db_user</emphasis> with at least
    386                   <emphasis>SELECT</emphasis>, <emphasis>INSERT</emphasis>,
    387                   <emphasis>UPDATE</emphasis>, <emphasis>DELETE</emphasis>,
    388                   <emphasis>CREATE</emphasis>, <emphasis>DROP</emphasis>,
    389                   <emphasis>INDEX</emphasis>,
    390                   and <emphasis>ALTER</emphasis> permission for the
    391                   new database. To do this, connect to your MySQL
    392                   server and issue the next lines:
    393 <programlisting>CREATE DATABASE base2 DEFAULT CHARACTER SET utf8;
    394 CREATE DATABASE base2dynamic DEFAULT CHARACTER SET utf8;
    395 GRANT ALL ON base2.* TO db_user@localhost IDENTIFIED BY 'db_password';
    396 GRANT ALL ON base2dynamic.* TO db_user@localhost;</programlisting>
    397                 </para>             
    398                 <para>
    399                   If you download BASE (instructions below) you find a file
    400                   <filename>&lt;base-dir&gt;/misc/sql/createdb.mysql.sql</filename>
    401                   that contains the above statements and can be used
    402                   by the <filename>mysql</filename> command-line tool
    403                   (remember to edit the <emphasis>db_user</emphasis>,
    404                   <emphasis>db_password</emphasis>, and the database
    405                   names in the script file before executing the
    406                   command): <command>mysql -uroot -p &lt;
    407                   &lt;base-dir&gt;/misc/sql/createdb.mysql.sql</command>. The
    408                   header in the script file contains further
    409                   information about the script.
    410353                </para>
    411354              </listitem>
  • trunk/doc/src/docbook/appendix/base.config.xml

    r7982 r7997  
    7272          <itemizedlist>
    7373          <listitem>
    74             <userinput>org.hibernate.dialect.MySQL5InnoDBDialect</userinput>
    75             for MySQL
    76           </listitem>
    77           <listitem>
    7874            <userinput>org.hibernate.dialect.PostgreSQL9Dialect</userinput>
    7975            for PostgreSQL
     
    9086        <para>
    9187          The connection URL that locates the BASE database. The exact syntax
    92           of the string depends on the JDBC driver. Here are two examples which
     88          of the string depends on the JDBC driver. Here is an example which
    9389          leaves all other settings to their defaults:
    9490          <itemizedlist>
    95           <listitem>
    96             <userinput>jdbc:mysql://localhost/basedb</userinput>
    97             for MySQL
    98           </listitem>
    9991          <listitem>
    10092            <userinput>jdbc:postgresql:basedb</userinput>
     
    10597          You can get more information about the parameters that are supported on the
    10698          connection URL by reading the documentation from
    107           <ulink url="http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html"
    108             >MySQL</ulink> and
    10999          <ulink url="http://jdbc.postgresql.org/documentation/81/connect.html"
    110100            >PostgreSQL</ulink>.
    111101           
    112            
    113           <note>
    114             <para>
    115             For MySQL we recommend that you set the character encoding to UTF-8
    116             and enable the server-side cursors feature. The latter option will
    117             reduce memory usage since the JDBC driver does not have to
    118             load all data into memory. The value below should go into one line
    119             <userinput>
    120             jdbc:mysql://localhost/basedb?characterEncoding=UTF-8&amp;useCursorFetch=true&amp;defaultFetchSize=100&amp;useServerPrepStmts=true
    121             </userinput>
    122             </para>
    123           </note>
    124            
    125102        </para>
    126103      </listitem>
     
    134111        analysed data is located. If not specified the same catalog as the regular
    135112        database is used. The exact meaning of catalog depends on the actual database.
    136         For MySQL the catalog is the name of the database so this value is simply the
    137         name of the dynamic database. PostgreSQL does not support connecting to multiple
     113        PostgreSQL does not support connecting to multiple
    138114        databases with the same connection so this should have the same value as the
    139115        database in the <property>db.url</property> setting.
     
    147123        <para>
    148124        The name of the schema where the dynamic database used to store
    149         analysed data is located. MySQL does not have schemas so this value should
    150         be left empty. PostgreSQL supports schemas and we recommend that the dynamic
     125        analysed data is located. PostgreSQL supports schemas and we recommend that the dynamic
    151126        part is created in it's own schema to avoid mixing the dynamic tables with
    152127        the regular ones.
  • trunk/doc/src/docbook/appendix/update_warnings.xml

    r7982 r7997  
    3535    to the current version.
    3636  </para>
     37
     38
     39  <sect1 id="appendix.update_warnings.3.19">
     40    <title>BASE 3.19</title>
     41   
     42    <bridgehead>Support for MySQL has ended</bridgehead>
     43    <para>
     44      BASE 3.18 was the last release that supported MySQL. Since 
     45      BASE 3.19 we are only testing and supporting PostgreSQL. BASE may still
     46      work with MySQL after that, but we recommend that existing installations
     47      are migrated to PostgreSQL as soon as possible.
     48    </para>
     49  </sect1>
     50
    3751
    3852  <sect1 id="appendix.update_warnings.3.18">
  • trunk/src/core/common-queries.xml

    r7638 r7997  
    3030  should add an entry into the file that is specific for your
    3131  particular database that overrides the query in this file.
    32   For example, for MySQL modify the mysql-queries.xml.
     32  For example, for PostgreSQL modify the postgresql-queries.xml.
    3333-->
    3434<predefined-queries>
Note: See TracChangeset for help on using the changeset viewer.