Changeset 7997
- Timestamp:
- Aug 9, 2021, 3:32:20 PM (2 years ago)
- Location:
- trunk
- Files:
-
- 5 edited
-
config/dist/base.config (modified) (1 diff)
-
doc/src/docbook/admin/installation.xml (modified) (4 diffs)
-
doc/src/docbook/appendix/base.config.xml (modified) (5 diffs)
-
doc/src/docbook/appendix/update_warnings.xml (modified) (1 diff)
-
src/core/common-queries.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/config/dist/base.config
r7822 r7997 33 33 db.queries = /postgres-queries.xml 34 34 35 # ----- 36 # MySQL 37 # ----- 35 # ------------------------------------- 36 # MySQL (not supported since BASE 3.19) 37 # ------------------------------------- 38 38 # db.dialect = org.hibernate.dialect.MySQL8Dialect 39 39 # 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 47 47 48 48 <important id="installation.upgrade.important"> 49 <title>Important information for upgrading to BASE 3.1 8</title>49 <title>Important information for upgrading to BASE 3.19</title> 50 50 <para> 51 51 This section list some important information that may or may not 52 52 apply when upgrading from the <emphasis>previous</emphasis> BASE 53 release to the current release (eg. 3.1 7 to 3.18). If you are54 upgrading from a BASE installation that is older (3.0-3.1 6)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) 55 55 you should also read <xref linkend="appendix.update_warnings" />. 56 56 </para> 57 57 58 <bridgehead>Support for MySQL is ending in BSE 3.19</bridgehead>58 <bridgehead>Support for MySQL has ended</bridgehead> 59 59 <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 that63 existing installationsare 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. 64 64 </para> 65 65 … … 272 272 url="http://www.hibernate.org/">Hibernate</ulink> for 273 273 object persistence to a relational database. Hibernate 274 supports many database engines, but so farwe only work275 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. 277 277 </para> 278 278 … … 289 289 pre-configured for PostgreSQL so there is no need to change database 290 290 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 not299 recommend that MySQL is used for new installations.300 Existing installation should migrate to PostgreSQL301 as soon as possible. See <xref linkend="installation.migrate" />.302 Download MySQL from303 <ulink url="http://www.mysql.com/" />. You need to304 be able to connect to the server over TCP, so305 the <emphasis>skip-networking</emphasis> option306 must <command>not</command> be used. The InnoDB307 table engine is also needed, so do not disable them308 (not that you would) but you may want to tune the309 InnoDB behaviour before creating BASE310 databases.311 312 You must edit your <filename><base-dir>/www/WEB-INF/classes/base.config</filename>313 file. Uncomment the settings for MySQL and314 comment out the settings for PostgreSQL.315 291 </para> 316 292 </listitem> … … 375 351 template1</command> The header in the script file 376 352 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 a385 <emphasis>db_user</emphasis> with at least386 <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 the391 new database. To do this, connect to your MySQL392 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 file400 <filename><base-dir>/misc/sql/createdb.mysql.sql</filename>401 that contains the above statements and can be used402 by the <filename>mysql</filename> command-line tool403 (remember to edit the <emphasis>db_user</emphasis>,404 <emphasis>db_password</emphasis>, and the database405 names in the script file before executing the406 command): <command>mysql -uroot -p <407 <base-dir>/misc/sql/createdb.mysql.sql</command>. The408 header in the script file contains further409 information about the script.410 353 </para> 411 354 </listitem> -
trunk/doc/src/docbook/appendix/base.config.xml
r7982 r7997 72 72 <itemizedlist> 73 73 <listitem> 74 <userinput>org.hibernate.dialect.MySQL5InnoDBDialect</userinput>75 for MySQL76 </listitem>77 <listitem>78 74 <userinput>org.hibernate.dialect.PostgreSQL9Dialect</userinput> 79 75 for PostgreSQL … … 90 86 <para> 91 87 The connection URL that locates the BASE database. The exact syntax 92 of the string depends on the JDBC driver. Here are two exampleswhich88 of the string depends on the JDBC driver. Here is an example which 93 89 leaves all other settings to their defaults: 94 90 <itemizedlist> 95 <listitem>96 <userinput>jdbc:mysql://localhost/basedb</userinput>97 for MySQL98 </listitem>99 91 <listitem> 100 92 <userinput>jdbc:postgresql:basedb</userinput> … … 105 97 You can get more information about the parameters that are supported on the 106 98 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> and109 99 <ulink url="http://jdbc.postgresql.org/documentation/81/connect.html" 110 100 >PostgreSQL</ulink>. 111 101 112 113 <note>114 <para>115 For MySQL we recommend that you set the character encoding to UTF-8116 and enable the server-side cursors feature. The latter option will117 reduce memory usage since the JDBC driver does not have to118 load all data into memory. The value below should go into one line119 <userinput>120 jdbc:mysql://localhost/basedb?characterEncoding=UTF-8&useCursorFetch=true&defaultFetchSize=100&useServerPrepStmts=true121 </userinput>122 </para>123 </note>124 125 102 </para> 126 103 </listitem> … … 134 111 analysed data is located. If not specified the same catalog as the regular 135 112 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 138 114 databases with the same connection so this should have the same value as the 139 115 database in the <property>db.url</property> setting. … … 147 123 <para> 148 124 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 151 126 part is created in it's own schema to avoid mixing the dynamic tables with 152 127 the regular ones. -
trunk/doc/src/docbook/appendix/update_warnings.xml
r7982 r7997 35 35 to the current version. 36 36 </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 37 51 38 52 <sect1 id="appendix.update_warnings.3.18"> -
trunk/src/core/common-queries.xml
r7638 r7997 30 30 should add an entry into the file that is specific for your 31 31 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. 33 33 --> 34 34 <predefined-queries>
Note: See TracChangeset
for help on using the changeset viewer.
