[Mysql-cocoa-commits] CVS: Documentation/website archives.html,1.2,1.3 index.html,1.16,1.17 install_
Brought to you by:
sergecohen
Menu
▾
▴
[Mysql-cocoa-commits] CVS: Documentation/website archives.html,1.2,1.3 index.html,1.16,1.17 install_mysql-4.0.14.html,1.1,1.2
|
From: Serge C. <ser...@us...> - 2003-08-30 13:43:28
|
Update of /cvsroot/mysql-cocoa/Documentation/website In directory sc8-pr-cvs1:/tmp/cvs-serv11721 Modified Files: archives.html index.html install_mysql-4.0.14.html Log Message: Some correction adn additions in the instructions for installation of MySQL-4.0.14 page. 2003-08-30; Serge Cohen. Index: archives.html =================================================================== RCS file: /cvsroot/mysql-cocoa/Documentation/website/archives.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** archives.html 27 Aug 2003 21:54:27 -0000 1.2 --- archives.html 30 Aug 2003 13:43:22 -0000 1.3 *************** *** 18,21 **** --- 18,29 ---- <a name="home"><p>Home page of the MySQL Cocoa project can be found <a href="index.html">here</a></p></a> + <p class="withlist"><em>18 August 2003:</em> Released the version 2.2.0 of the framework. The API is kept unchanged, the main difference is in the project organisation (in Project Builder). I also have tried to make the aim of each target more clear, and cleaned up the build-styles, in that respect I have defined 3 different names for each of the flavours (corresponding to 3 different targets) of the framework (which BTW have also changed):</p> + <ol class="intext"> + <li class="intext"><em>SMySQL :</em> A <em>system-wide</em> framework, using the <em>dynamic</em> version of libmysqlclient.</li> + <li class="intext"><em>SMySQL_static :</em> A <em>system-wide</em> framework, using the <em>static</em> version of libmysqlclient.</li> + <li class="intext"><em>SMySQL_bundled :</em> A <em>bundled</em> framework (for bundling within Cocoa application), using the <em>static</em> version of libmysqlclient.</li> + </ol> + <p class="afterwithlist">Also modified the way the libmysqlclient static library is used, now a binary version of the library is distributed with the sources of the framework (the sources of the libmysqlclient used to be included in the project and compiled when building the framework). This way makes it easier if someone prefers to use it's own version of the libmysqlcleint library.</p> + <p class="withlist"><em>24 December 2002:</em> Posted the file releases for the version 2.0 of the framework. This correspond to both a source and a binary release. This version of the framework has a new API:</p> <ul class="intext"> *************** *** 116,118 **** --- 124,129 ---- <div class="center"><A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=42424&type=1" width="88" height="31" border="0" alt="SourceForge Logo"></A></div> + <hr> + <p class="footer">This page and its contents (unless otherwise noted or implied) Copyright © 2002 Serge Cohen. You can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <a href="gpl.html">GNU General Public License</a> for more details.</p> </BODY> + </HTML> Index: index.html =================================================================== RCS file: /cvsroot/mysql-cocoa/Documentation/website/index.html,v retrieving revision 1.16 retrieving revision 1.17 diff -C2 -d -r1.16 -r1.17 *** index.html 27 Aug 2003 21:54:27 -0000 1.16 --- index.html 30 Aug 2003 13:43:22 -0000 1.17 *************** *** 29,32 **** --- 29,34 ---- <a name="archive"><p>Archives of the updates can be found <a href="archives.html">here</a></p></a> + <p><em>30 August 2003:</em> Added some comments and a last section (reloading data from the mysqldump file) to the instructions on how to install MySQL frmo sources. The file released has been updated to this new documentation as well.</p> + <p><em>27 August 2003:</em> Added a documentation on how to build MySQL from sources. You will find a link to these inscription in the <a href="#docs">Documentation</a> section. Following these instructions you should be able to build MySQL server and client sides, with prebound dynamic libraries (as well as static libraries), openssl support for both server and client... and finally getting the <code>libmysqld.a</code> library which is basically a embedded MySQL server running in its own thread, so your program can contains its own server (not yet supported by SMySQL framework... but might come some time soon).</p> *************** *** 35,46 **** <p><em>20 August 2003:</em> Releases the version 2.2.1 of the framework: minor bug correction. The previous versions of the framework were not able to handle properly the integer with more than 32bits (MySQL BIGINT). This is now corrected (indeed the other branches of the framework are also corrected in CVS, so if you are still using the version 1, I encourage you to get the fix from CVS). Unfortunately I have not found a solution to know from the MySQL server if an retrieve integer is signed or not, hence the framework assumes always signed int: this can cause a trouble if you have a unsigned column (either for BIGINT or INT) and you are using number bigger than the maximum SIGNED number. Thanks to Lorenz Textor for pointing the bug to me.</p> - <p class="withlist"><em>18 August 2003:</em> Released the version 2.2.0 of the framework. The API is kept unchanged, the main difference is in the project organisation (in Project Builder). I also have tried to make the aim of each target more clear, and cleaned up the build-styles, in that respect I have defined 3 different names for each of the flavours (corresponding to 3 different targets) of the framework (which BTW have also changed):</p> - <ol class="intext"> - <li class="intext"><em>SMySQL :</em> A <em>system-wide</em> framework, using the <em>dynamic</em> version of libmysqlclient.</li> - <li class="intext"><em>SMySQL_static :</em> A <em>system-wide</em> framework, using the <em>static</em> version of libmysqlclient.</li> - <li class="intext"><em>SMySQL_bundled :</em> A <em>bundled</em> framework (for bundling within Cocoa application), using the <em>static</em> version of libmysqlclient.</li> - </ol> - <p class="afterwithlist">Also modified the way the libmysqlclient static library is used, now a binary version of the library is distributed with the sources of the framework (the sources of the libmysqlclient used to be included in the project and compiled when building the framework). This way makes it easier if someone prefers to use it's own version of the libmysqlcleint library.</p> - <!--/Updates--> --- 37,40 ---- *************** *** 83,87 **** <a name="docs"><h2>Documentation</h2></a> ! <p>Some of the documentation available Online can be found <a href="http://sourceforge.net/docman/index.php?group_id=42424">here on Sourceforge</a> (indeed not yet); the rest is below.</p> <h4>Building MySQL from sources</h4> --- 77,84 ---- <a name="docs"><h2>Documentation</h2></a> ! <p>Ideally some documentation would be available on the <a href="http://sourceforge.net/docman/index.php?group_id=42424">sourceforge docman</a>... Unfortunately I did not had time to do so, so it's here.</p> ! ! <h4>Framework API documentation.</h4> ! <p>The framework comes with its own documentation (in the Resources/English.lproj/Documentation/Classes directory of the compiled frameworks). It is coming directly from the sources using the <a href="http://www.misckit.com/press/press_autodoc_2.0b8.html">autodoc application</a>. This same generated documentation can be found <a href="SMySQL_doc/">online here</a> (corresponding to the last version of the framework).</p> <h4>Building MySQL from sources</h4> *************** *** 200,204 **** <hr> ! <p class="footer">This page and its contents (unless otherwise noted or implied) Copyright © 2002 MySQL Cocoa Project. You can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <a href="gpl.html">GNU General Public License</a> for more details.</p> </BODY> </HTML> --- 197,201 ---- <hr> ! <p class="footer">This page and its contents (unless otherwise noted or implied) Copyright © 2002 Serge Cohen. You can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <a href="gpl.html">GNU General Public License</a> for more details.</p> </BODY> </HTML> Index: install_mysql-4.0.14.html =================================================================== RCS file: /cvsroot/mysql-cocoa/Documentation/website/install_mysql-4.0.14.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** install_mysql-4.0.14.html 27 Aug 2003 21:54:27 -0000 1.1 --- install_mysql-4.0.14.html 30 Aug 2003 13:43:22 -0000 1.2 *************** *** 48,51 **** --- 48,53 ---- </div> + <p><a name="foreign_key_note"><em>NOTE </em>: If you are using some InnoDB databases, and have some constraints on foreign keys, then you might have to edit your mysqldump file, so that if a table B reference a key in table A, then table A definition (and content) appears first in the mysqldump output... Unfortunately mysqldump does not take care of that for you (indeed it output the tables in alphabetic order), so it is likely that some table appear in the output <em>before</em> the table it is referencing, causing a <code>ERROR 1005 at line ...: Can't create table './..../.....frm' (errno: 150)</code>. Then the solution is as easy as editing the mysqldump file to make sure that the table are defined in dependency order.</a></p> + <p>Now if you want to be sure that you don't mix two different installation of the database (if you are a bit paranoiac...), you can shutdown the server and remove all the files which where installed. Assuming your previous installation was also from sources (with prefix set to <code>/usr/local</code>) that would give something like:</p> *************** *** 175,178 **** --- 177,181 ---- <pre>% <b>su - mysql</b> Password: <i>type mysql user password</i> + % <b>mv </b><i>DB_data OLD_DB_data</i> % <b>mkdir </b><i>DB_data</i> % <b>exit</b> *************** *** 180,187 **** </div> <p>Now install the binaries, libraries, include files...</p> <div class="code"> <pre>% <b>sudo make install</b> ! Password: <i>type root(system) password</i> % </pre> </div> --- 183,192 ---- </div> + <p>The line <code><b>mv </b><i>DB_data OLD_DB_data</i></code> has for purpose to backup your old database directory ... you might want to delete this old directory once the new server is up and running, and that you have checked that the data is OK.</p> + <p>Now install the binaries, libraries, include files...</p> <div class="code"> <pre>% <b>sudo make install</b> ! Password: <i>type your(system – you have to be in the sudoer group –) password</i> % </pre> </div> *************** *** 217,228 **** ! <h2>5. Bonnus</h2> <p>In the disk image you will also find a configuration file (<code>Serge_my.cnf</code>) for your mysql server... there should be a couple of these examples already there (in <code>/Users/mysql/DB_data</code>). The one I give away is set in a reasonable way for a small server using InnoDB and having to transfer big files to and fro some client (be it SMySQL framework based oreven PHP). To use it just copy it in the <code>/Users/mysql/DB_data</code> directory and change its name to <code>my.cnf</code> (it is better to do this while the MySQL server down).</p> <h2><a name="files">File</a></h2> <ul> ! <li>All you need (on top of the MySQL sources :-) ) is this disk image: <a href="http://prdownloads.sourceforge.net/mysql-cocoa/install_mysql-4.0.14.dmg?download">install_mysql-4.0.14.dmg</a> </li> </ul> --- 222,250 ---- ! <h2>5. Reloading your data</h2> ! ! <p>We are going to use the big mysqldump file generated at step 1 to reload the database with your previous data:</p> ! ! <div class="code"> ! <pre>% <b>cd </b><i>in/some/safe/directory</i> ! % <b>mysql -u root </b><i>Data_YYYY-MM-DD</i><b>.mysql</b> ! % ! </pre> ! </div> ! ! <p><em>Note </em>: if you are using InnoDB databases, this last command might produce some error (and partial reload of your data). The reason for this error (as the fix) is explained in the first section, in <a href="#foreign_key_note">this paragraph</a>.</p> ! ! <h2>6. Bonnus</h2> <p>In the disk image you will also find a configuration file (<code>Serge_my.cnf</code>) for your mysql server... there should be a couple of these examples already there (in <code>/Users/mysql/DB_data</code>). The one I give away is set in a reasonable way for a small server using InnoDB and having to transfer big files to and fro some client (be it SMySQL framework based oreven PHP). To use it just copy it in the <code>/Users/mysql/DB_data</code> directory and change its name to <code>my.cnf</code> (it is better to do this while the MySQL server down).</p> + <h2>Later ...</h2> + + <p>As soon as I have time, I will explain how to use ssl to communicate with the mysql server you have just set up...</p> + <h2><a name="files">File</a></h2> <ul> ! <li>All you need (on top of the MySQL sources :-) ) is this disk image: <a href="http://prdownloads.sourceforge.net/mysql-cocoa/install_mysql-4.0.14-r2.dmg?download">install_mysql-4.0.14-r2.dmg</a> </li> </ul> |
