mromy 2005/05/03 18:56:34 CEST
Modified files:
html README.html
Log:
- added some new warnings
Revision Changes Path
1.9 +33 -24 jahia_update/html/README.html
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia_update/html/README.html.diff?r1=1.8&r2=1.9&f=h
Index: README.html
===================================================================
RCS file: /cvs/jahia_update/html/README.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- README.html 2 May 2005 13:13:26 -0000 1.8
+++ README.html 3 May 2005 16:56:34 -0000 1.9
@@ -71,7 +71,9 @@
<p><strong>1) Copy the JahiaUpdate_4_1.jar file to the following
directory:</strong></p>
<p class="code">[install_path]/tomcat/webapps/jahia</p>
<p><strong>2) Make sure tomcat is stopped and that the database is
running and available (excepted for the
- embedded Hypersonic database, which is the database used by
Jahia by default).</strong> </p>
+ embedded Hypersonic database, which is the database used by
Jahia by default).<br/><br/> Under Unix/Linux,
+ make sure that you are running the patch under the same user
that is running Jahia, you may otherwise encounter
+ some directories permissions issues.</strong> </p>
<p><strong>3) To start the upgrading process, type on the command
line:</strong></p>
<p class="code"> java -jar JahiaUpdate_4_1.jar</p>
<p>
@@ -127,23 +129,46 @@
you may have developed or integrated are standalone seperate web
applications.<br/>
</p>
<br/>
- <a name="2"></a><h2>Upgrade issues</h2>
+ <a name="2"></a><h2>Upgrade issues with MySQL</h2>
+
+ <h2 class="red">Please read carefully this part as it contains
needed information to alter the settings of
+ the MySQL database to allow the upgrade tool to complete
successfully</h2>
If you are using MySQL database, the upgrade tool will also need to
ensure that some new tables that
are created during the process are in a certain table type, namely
<strong>InnoDB</strong>. If you are using
MySQL 4.1, there should not be any problems as new tables are
created by default in <strong>InnoDB</strong> format.
However, with MySQL 4.0 default table format is
<strong>MyISAM</strong>. During the upgrade process, the tool will
- try to change this type as it creates the new tables, however in
some cases we noticed that the command has no effect
- , so you may need to manually alter the type of the tables
created.<br/><br/>
- To check if the new tables (all tables beginning with "jahia_sl2")
are in of the correct type, issue the following
+ try to change this type as it creates the new tables, however in
some cases we noticed that the command has no effect.
+ <br/><br/>
+ The best way to ensure that the tables will be created in the
correct format during the upgrade process is to change
+ the settings of MySQL in the configuration file
(<em>my.cnf</em>/<em>my.ini</em>) to set the default type for new tables
+ to InnoDB before executing the upgrade tool. <br/>
+ Edit the <em>my.cnf</em>(linux) or <em>my.ini</em>(windows) and add
the following line in the [mysqld] part of the file :<br/>
+ <p class="code">
+ default-table-type=InnoDB
+ </p>
+ If your database server runs under <strong>Linux</strong>, you also
<span class="red"><strong>need</strong></span> to change a default setting to
allow case-insensitive
+ SQL requests.
+ Under Windows and MacOSX, case-insensitive SQL requests are
activated by default, but not under Linux, so you need to edit the
+ <em>my.cnf</em> configuration file of MySQL and add the following
statement in the [mysqld] part of the file :
+ <p class="code">
+ lower_case_table_names=1
+ </p>
+
+ Then restart your MySQL instance. You can now launch the jahia
upgrade tool. New tables will now be
+ created by default in InnoDB format. <br/><br/>
+ <p>
+
+ To check if the new tables (all tables beginning with "jahia_sl2")
are of the correct type, issue the following
sql command once logged into you MySQL database :<br/>
<br/>
<p class="code">SHOW TABLE STATUS FROM your_database LIKE
'jahia_sl2%';</p>
<br/>
This should display the status of all tables beginning with
"jahia_sl2". The column "Type" will give you the current format
- of the tables. If the type is "InnoDB", then the upgrade tool has
been able to successfully alter the table format.
- If however the type is "MyISAM", you will need to change manually
the format of all "jahia_sl2" tables by issuing the
- following SQL commands : <br/>
+ of the tables. <br/>
+ If the type is "InnoDB", then the upgrade tool has been able to
successfully alter the table format.
+ If however the type is still "MyISAM" for whatever reason, you will
need to change manually the format of all "jahia_sl2"
+ tables by issuing the following SQL commands : <br/>
<p class="code">
ALTER TABLE jahia_sl2_uri type=innodb;<br/>
ALTER TABLE jahia_sl2_object type=innodb;<br/>
@@ -163,22 +188,6 @@
<br/>
You can then re-issue the previous "SHOW TABLE STATUS" command to
ensure the tables are now of the correct type.
<br/><br/>
- Another way to ensure that the tables will be created in the correct
format during the upgrade process is to change
- the settings of MySQL in the configuration file (my.cnf/my.ini) to
set the default type for new tables
- to InnoDB before executing the upgrade tool. <br/>
- Edit the my.cnf(linux) or my.ini(windows) and add the following line
in the [mysqld] part of the file :<br/>
- <p class="code">
- default-table-type=InnoDB
- </p>
- Then restart your MySQL instance. You can now launch the jahia
upgrade tool. New tables will now be
- created by default in InnoDB format. <br/><br/>
- <p>
- If you have problems installing this update, check the Install
mailing
- list (<a
href="http://www.jahia.org/install_list";>http://www.jahia.org/install_list</a>).
- In case you don't find suitable answers, be sure to include your
environnement
- information (OS, database used, problems encountered, error
message displayed,...)
- when submitting your question.<br/>
- </p>
<br/>
<a name="3"></a><h2>Upgrading to MySQL 4.1.x</h2>
<p>
