Author: shinz
Date: 2007-10-30 13:01:51 +0100 (Tue, 30 Oct 2007)
New Revision: 8401
Log:
Created snapshot for upcoming Thai translation
Added:
trunk/th/VERSION
trunk/th/administrator/Makefile
trunk/th/administrator/Makefile.depends
trunk/th/administrator/administrator.xml
trunk/th/administrator/all-entities.ent
trunk/th/administrator/backup.xml
trunk/th/administrator/catalogs.xml
trunk/th/administrator/chapter-options-administrator.xml
trunk/th/administrator/connection-dialog.xml
trunk/th/administrator/health.xml
trunk/th/administrator/images/published/README
trunk/th/administrator/images/published/backup-completed.png
trunk/th/administrator/images/published/backup-content.png
trunk/th/administrator/images/published/backup-progress.png
trunk/th/administrator/images/published/configure-service-mode-connection.png
trunk/th/administrator/images/published/configure-service-mode-window.png
trunk/th/administrator/images/published/connection.png
trunk/th/administrator/images/published/error.png
trunk/th/administrator/images/published/graph-settings.png
trunk/th/administrator/images/published/mainwindow.png
trunk/th/administrator/images/published/marked-area.png
trunk/th/administrator/images/published/options-connections.png
trunk/th/administrator/images/published/options-general-options.png
trunk/th/administrator/images/published/replication.png
trunk/th/administrator/images/published/restore-content.png
trunk/th/administrator/images/published/server-logs-general-log.png
trunk/th/administrator/images/published/system-tray.png
trunk/th/administrator/images/published/user-accounts.png
trunk/th/administrator/images/published/user-information.png
trunk/th/administrator/introduction.xml
trunk/th/administrator/legalnotice.en.xml
trunk/th/administrator/main-window.xml
trunk/th/administrator/replication-status.xml
trunk/th/administrator/restore.xml
trunk/th/administrator/server-connections.xml
trunk/th/administrator/server-information.xml
trunk/th/administrator/server-logs.xml
trunk/th/administrator/service-control.xml
trunk/th/administrator/startup-variables.xml
trunk/th/administrator/tray-monitor.xml
trunk/th/administrator/user-administration.xml
trunk/th/administrator/xml-files.xml
trunk/th/common/fixedchars.ent
trunk/th/common/phrases.ent
trunk/th/gui-common/Makefile
trunk/th/gui-common/Makefile.depends
trunk/th/gui-common/all-entities.ent
trunk/th/gui-common/appendix-common-files.xml
trunk/th/gui-common/appendix-connection-storage.xml
trunk/th/gui-common/appendix-source-install.xml
trunk/th/gui-common/appendix-third-party.xml
trunk/th/gui-common/appendix-translator-notes.xml
trunk/th/gui-common/appendix-troubleshooting.xml
trunk/th/gui-common/chapter-grt-shell.xml
trunk/th/gui-common/chapter-options-connections.xml
trunk/th/gui-common/chapter-options-editors.xml
trunk/th/gui-common/chapter-options-general.xml
trunk/th/gui-common/chapter-options-introduction.xml
trunk/th/gui-common/chapter-table-editor.xml
trunk/th/gui-common/chapter-uninstall-all.xml
trunk/th/gui-common/chapter-upgrade-all.xml
trunk/th/gui-common/gui-common.ent
trunk/th/gui-common/images/published/README
trunk/th/gui-common/images/published/columneditor.png
trunk/th/gui-common/images/published/confirmchanges.png
trunk/th/gui-common/images/published/connectionerror.png
trunk/th/gui-common/images/published/grt-shell.png
trunk/th/gui-common/images/published/indexeditor.png
trunk/th/gui-common/images/published/options-connection.png
trunk/th/gui-common/images/published/options.png
trunk/th/gui-common/images/published/ssl-params.png
trunk/th/gui-common/images/published/tableeditor.png
trunk/th/gui-common/installation-all.xml
trunk/th/gui-common/mysql-enterprise.xml
trunk/th/gui-common/starting-all.xml
trunk/th/query-browser/Makefile
trunk/th/query-browser/Makefile.depends
trunk/th/query-browser/all-entities.ent
trunk/th/query-browser/chapter-options-query-browser.xml
trunk/th/query-browser/connection-dialog.xml
trunk/th/query-browser/images/published/README
trunk/th/query-browser/images/published/blob-buttons.png
trunk/th/query-browser/images/published/buttonbar.png
trunk/th/query-browser/images/published/connection.png
trunk/th/query-browser/images/published/dynamiclist.png
trunk/th/query-browser/images/published/file-open-script.png
trunk/th/query-browser/images/published/gui-command-line.png
trunk/th/query-browser/images/published/mainscreen.png
trunk/th/query-browser/images/published/qb-options.png
trunk/th/query-browser/images/published/querybar.png
trunk/th/query-browser/images/published/schematabrowser.png
trunk/th/query-browser/images/published/script-editor.png
trunk/th/query-browser/images/published/stored-procedure-database-browser.png
trunk/th/query-browser/images/published/tabletool.png
trunk/th/query-browser/images/published/twosakilas.png
trunk/th/query-browser/introduction.xml
trunk/th/query-browser/legalnotice.en.xml
trunk/th/query-browser/metadata/chapter-options-query-browser.idmap
trunk/th/query-browser/metadata/connection-dialog.idmap
trunk/th/query-browser/metadata/introduction.idmap
trunk/th/query-browser/metadata/legalnotice.en.idmap
trunk/th/query-browser/metadata/options.idmap
trunk/th/query-browser/metadata/query-browser.idmap
trunk/th/query-browser/metadata/tour.idmap
trunk/th/query-browser/metadata/using.idmap
trunk/th/query-browser/metadata/xml-files.idmap
trunk/th/query-browser/options.xml
trunk/th/query-browser/query-browser.xml
trunk/th/query-browser/tour.xml
trunk/th/query-browser/using.xml
trunk/th/query-browser/xml-files.xml
Property changes on: trunk/th/administrator/connection-dialog.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/administrator/images/published/README
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/administrator/images/published/backup-completed.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/backup-content.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/backup-progress.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/configure-service-mode-connection.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/configure-service-mode-window.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/connection.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/error.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/graph-settings.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/mainwindow.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/marked-area.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/options-connections.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/options-general-options.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/replication.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/restore-content.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/server-logs-general-log.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/system-tray.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/user-accounts.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/administrator/images/published/user-information.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/chapter-grt-shell.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/gui-common/chapter-uninstall-all.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/gui-common/images/published/columneditor.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/confirmchanges.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/connectionerror.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/grt-shell.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/indexeditor.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/options-connection.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/options.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/ssl-params.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/images/published/tableeditor.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/gui-common/installation-all.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/gui-common/starting-all.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/query-browser/connection-dialog.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/th/query-browser/images/published/blob-buttons.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/buttonbar.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/connection.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/dynamiclist.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/file-open-script.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/gui-command-line.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/mainscreen.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/qb-options.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/querybar.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/schematabrowser.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/script-editor.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/stored-procedure-database-browser.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/tabletool.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/th/query-browser/images/published/twosakilas.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/th/VERSION
===================================================================
--- trunk/th/VERSION (rev 0)
+++ trunk/th/VERSION 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 584 bytes
@@ -0,0 +1,11 @@
+Pfad: .
+URL: svn+ssh://shinz@stripped/svn/mysqldoc/trunk
+Basis des Projektarchivs: svn+ssh://shinz@stripped/svn/mysqldoc
+UUID des Projektarchivs: c493bd56-8c02-0410-a43f-aded7e9288fb
+Revision: 8400
+Knotentyp: Verzeichnis
+Plan: normal
+Letzter Autor: shinz
+Letzte geänderte Rev: 8400
+Letztes Änderungsdatum: 2007-10-30 11:54:06 +0100 (Di, 30 Okt 2007)
+
Added: trunk/th/administrator/Makefile
===================================================================
--- trunk/th/administrator/Makefile (rev 0)
+++ trunk/th/administrator/Makefile 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 60, Lines Deleted: 0; 1787 bytes
@@ -0,0 +1,60 @@
+# Makefile for MySQL Administrator manual
+
+# Location of repository root relative to current directory
+REPO_ROOT = ../..
+
+# Location of directory containing Makefile components
+MAKE_DIR = $(REPO_ROOT)/make.d
+
+# Set any variables here that should override imported standard variables
+
+DOC_LANG = en
+MAIN_DOC_BASENAME = administrator
+
+# Set IDMAP and remap variables
+
+IDMAP_LANG = $(DOC_LANG)
+IDMAP_MAIN = administrator
+
+IDMAP_URLBASE = $(IDMAP_MAIN)/$(IDMAP_LANG)
+IDMAP_REFS = . $(REPO_ROOT)/gui-common $(REPO_ROOT)/refman-5.1 $(REPO_ROOT)/refman-common
+IDMAP_SRCS = $(call base_xml_files)
+
+# Import standard variables
+
+include $(MAKE_DIR)/vars-layout
+include $(MAKE_DIR)/vars-shell
+include $(MAKE_DIR)/vars-docbook
+
+# Import default target rule (causes help message to print)
+
+include $(MAKE_DIR)/default-target
+
+# Files for which to generate dependencies
+DEPEND_FILES = administrator.xml
+
+# Import document dependency specifications
+
+include Makefile.depends
+
+# Import standard target rules
+
+include $(MAKE_DIR)/xml-valid
+include $(MAKE_DIR)/xml-format
+include $(MAKE_DIR)/xml-useless
+include $(MAKE_DIR)/xml-prep
+include $(MAKE_DIR)/xml-html
+include $(MAKE_DIR)/xml-html-section
+include $(MAKE_DIR)/xml-html-chapter
+include $(MAKE_DIR)/xml-html-web
+include $(MAKE_DIR)/xml-chm
+#include $(MAKE_DIR)/xml-xhtml
+include $(MAKE_DIR)/xml-pdf
+include $(MAKE_DIR)/xml-toc
+#include $(MAKE_DIR)/xml-txt
+include $(MAKE_DIR)/xml-info
+include $(MAKE_DIR)/xml-depend
+
+# Import directory specific extensions
+
+include $(MAKE_DIR)/Makefile.ext
Added: trunk/th/administrator/Makefile.depends
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 113 bytes
Added: trunk/th/administrator/administrator.xml
===================================================================
--- trunk/th/administrator/administrator.xml (rev 0)
+++ trunk/th/administrator/administrator.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 136, Lines Deleted: 0; 5020 bytes
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<book id="mysql-administrator" lang="en">
+
+<!--
+If 'indexterm' elements are added to this document sometime, add an
+empty 'index/' element before the closing '/book' tag to enable
+index-generation. Right now there is no such element because there
+is no point in generating an empty index.
+-->
+
+ <title>&administrator;</title>
+
+ <bookinfo>
+
+ <title>&administrator;</title>
+
+ <abstract>
+
+ <para>
+ This is the &administrator; Manual.
+ </para>
+
+ <para>
+ Document generated on:
+
+<?dbtimestamp format="Y-m-d"?>
+
+ <remark role="repository.revision"/>
+ </para>
+
+ </abstract>
+
+ <xi:include href="legalnotice.en.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ </bookinfo>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/mysql-enterprise.xml"/>
+
+ <xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/installation-all.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-uninstall-all.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-upgrade-all.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/starting-all.xml"/>
+
+ <xi:include href="connection-dialog.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="main-window.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="server-information.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="service-control.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="startup-variables.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="server-connections.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="user-administration.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="health.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="server-logs.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="backup.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="restore.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="replication-status.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include href="catalogs.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-table-editor.xml"/>
+
+ <chapter id="mysql-gui-options">
+
+ <title>Options Dialog</title>
+
+<!--
+ Include sections that are shared in common between administrator and
+ query-browser documents, then the final document-specific section.
+-->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-options-introduction.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="chapter-options-administrator.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-options-general.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-options-connections.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/chapter-options-editors.xml"/>
+
+ </chapter>
+
+<!-- END OPTIONS CHAPTER -->
+
+ <xi:include href="tray-monitor.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+<!--INSERT SOURCE INSTALL APPENDIX -->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/appendix-source-install.xml"/>
+
+<!-- INSERT THE TROUBLESHOOTING APPENDIX -->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/appendix-troubleshooting.xml"/>
+
+<!-- INSERT THE CONNECTION STORAGE APPENDIX -->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/appendix-connection-storage.xml"/>
+
+<!-- INSERT THE COMMON FILES APPENDIX -->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/appendix-common-files.xml"/>
+
+<!-- XML Files Used by &administrator; -->
+
+ <xi:include href="xml-files.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+<!-- INSERT THE NOTES FOR TRANSLATORS APPENDIX -->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/appendix-translator-notes.xml"/>
+
+<!-- INSERT THIRD PARTY TOOLS APPENDIX -->
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../gui-common/appendix-third-party.xml"/>
+
+</book>
Added: trunk/th/administrator/all-entities.ent
===================================================================
--- trunk/th/administrator/all-entities.ent (rev 0)
+++ trunk/th/administrator/all-entities.ent 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 694 bytes
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+ This file names all the entity files needed by .xml files in the
+ current directory. All ENTITY declarations should be given
+ first, followed by references to the those entities.
+-->
+<!ENTITY % fixedchars.entities SYSTEM "../common/fixedchars.ent">
+<!ENTITY % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+%fixedchars.entities;
+%gui-common.entities;
Added: trunk/th/administrator/backup.xml
===================================================================
--- trunk/th/administrator/backup.xml (rev 0)
+++ trunk/th/administrator/backup.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 341, Lines Deleted: 0; 12776 bytes
@@ -0,0 +1,341 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-backup">
+
+ <title>Backup</title>
+
+ <section id="mysql-administrator-backup-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ This section shows you how to create backup projects and to
+ perform backups. This section will produce backup files that are
+ plain text and composed of multiple SQL statements that can be
+ executed to restore your database, similar to the output generated
+ by the <literal>mysqldump</literal> utility. For more information
+ on <literal>mysqldump</literal>, see <xref linkend="mysqldump"/>,
+ in the reference manual.
+ </para>
+
+ <para>
+ Existing backup projects are listed in the lower left area of the
+ <link linkend="mysql-administrator-sidebar">sidebar</link>. If
+ there are many backup projects, the field with the magnifying
+ glass icon can be used to filter the projects you are looking for.
+ Typing in <literal>t</literal> or <literal>T</literal>, for
+ example, will set the filter to projects whose names begin with a
+ <literal>t</literal>. The filter works in a case-insensitive
+ fashion.
+ </para>
+
+ <para>
+ You can update the list of backup projects by right clicking on a
+ project and choosing the <guimenu>Refresh Backup
+ Projects</guimenu> option from the drop-down menu. You can delete
+ a backup project by right clicking on the project and choosing the
+ <guimenu>Delete Backup Project(s)</guimenu> option from the
+ drop-down menu.
+ </para>
+
+ <para>
+ If you are not working from a previously saved backup project,
+ click the <guibutton>New Project</guibutton> button to create a
+ new backup project. You cannot begin configuring a backup
+ operation without either loading an existing project or creating a
+ new project.
+ </para>
+
+ <para>
+ Once you have configured your backup project, you can click the
+ <guibutton>Save Project</guibutton> button to save your project
+ for future use. To start your backup, click the <guibutton>Execute
+ Backup Now</guibutton> button. You will be prompted for a path and
+ filename for the backup file, after which the backup operation
+ will begin.
+ </para>
+
+ </section>
+
+<!-- END INTRODUCTION -->
+
+ <section id="mysql-administrator-backup-backup-project">
+
+ <title>Backup Project</title>
+
+ <para>
+ The <guilabel>Backup Project</guilabel> tab allows you to set the
+ name of your backup project and also determine what data will be
+ backed up.
+ </para>
+
+ <para>
+ You can name your project by filling out a name in the
+ <guilabel>Project Name</guilabel> field. If you have enabled the
+ <guilabel>Add Date/Time to Backup Files</guilabel> option in the
+ <literal>Administrator Options</literal> dialog then the date and
+ time of the backup will be appended to the project name
+ automatically. See
+ <xref linkend="mysql-gui-options-administrator-backup" /> for more
+ information on setting this option.
+ </para>
+
+ <para>
+ Specify a name that clearly identifies the project, such as
+ <literal>Full Backup</literal> or <literal>World Only</literal>.
+ The project name may contain arbitrary characters, including
+ spaces.
+ </para>
+
+ <para>
+ To choose the databases and tables that will be backed up, select
+ the database from the schemata list and click the
+ <guibutton>></guibutton> button. Once the database is in the
+ <literal>Backup Content</literal> list, you can uncheck specific
+ tables that you do not wish to back up.
+ </para>
+
+ </section>
+
+<!-- END BACKUP PROJECT -->
+
+ <section id="mysql-administrator-backup-advanced-options">
+
+ <title>Advanced Options</title>
+
+ <para>
+ The <guilabel>Advanced Options</guilabel> tab allows you to
+ configure advanced options that affect the way the backup
+ operation behaves. These include concurrency controls, backup
+ type, and output formatting.
+ </para>
+
+ <section id="mysql-administrator-backup-advanced-options-execution-method">
+
+ <title>Backup Execution Method</title>
+
+ <para>
+ The <literal>Backup Execution Method</literal> affects
+ concurrency within the backup itself.
+ </para>
+
+ <para>
+ <guilabel>InnoDb Online Backup</guilabel> will begin a
+ transaction before reading from the tables. Because of the
+ InnoDB versioning system this will allow all tables to be read
+ in a consistent state. This method is recommended when backing
+ up InnoDB tables.
+ </para>
+
+ <para>
+ <guilabel>Lock all tables</guilabel> will cause all tables
+ within the backup to be locked simultaneously to prevent
+ writing. This will prevent users from writing to the tables
+ during the backup operation and will ensure that the tables are
+ in a consistent state. This option is recommended for MyISAM
+ tables.
+ </para>
+
+ <para>
+ <guilabel>Normal Backup</guilabel> will lock each table
+ individually when performing the backup. While this can have
+ less impact on the actions of users during the backup operation,
+ these is a potential for tables to be backed up in an
+ inconsistent state in relation to one another. This method is
+ not recommended unless the risk of inconsistency is minimal.
+ </para>
+
+ <para>
+ <guilabel>Online with binlog pos</guilabel> is the same as
+ <literal>InnoDb Online Backup</literal> but also logs the
+ current position within the binary log.
+ </para>
+
+ <para>
+ <guilabel>Complete Backup</guilabel> overrides the table
+ selection made in the <guilabel>Backup Project</guilabel> tab
+ and backs up all tables in the selected schema. This option can
+ be useful when scheduling the backup of a schema that changes
+ regularly.
+ </para>
+
+ </section>
+
+<!-- END EXECUTION METHOD -->
+
+ <section id="mysql-administrator-backup-advanced-options-output-options">
+
+ <title>Output File Options</title>
+
+ <para>
+ The <guilabel>Output File Options</guilabel> section controls
+ the formatting of the backup file. At present there is only one
+ <literal>Backup Type</literal> available, the <literal>SQL
+ Files</literal> format, which outputs a file similar to the
+ output of the <literal>mysqldump</literal> utility.
+ </para>
+
+ <para>
+ <guilabel>No CREATEs</guilabel> will suppress <literal>CREATE
+ DATABASE</literal> statements. This can be useful if you need to
+ restore the data to a different database than it was backed up
+ from.
+ </para>
+
+ <para>
+ <guilabel>No EXTENDED INSERTS</guilabel> will suppress the
+ default behavior of combining multiple inserts into a single
+ statement (for example <literal>INSERT INTO test VALUES
+ ('1',Some data',2234),('2','Some More Data',23444)</literal>).
+ While the <literal>EXTENDED INSERT</literal> syntax is more
+ efficient both in terms of storage and execution, it is not
+ compatible with most RDBMSes.
+ </para>
+
+ <para>
+ <guilabel>Add DROP Statements</guilabel> adds <literal>DROP
+ TABLE IF EXISTS</literal> statements to the backup file.
+ </para>
+
+ <note>
+ <para>
+ If your backup project includes views then you
+ <emphasis>must</emphasis> choose this option. Restoration of a
+ view is a two step process that involves creating a dummy
+ table with the same name as the view. This table must be
+ dropped before the view can be recreated.
+ </para>
+ </note>
+
+ <para>
+ <guilabel>Complete INSERTs</guilabel> will produce full
+ <literal>INSERT</literal> statements that include a column list
+ (i.e. <literal>INSERT INTO tablename(columnA, columnB)
+ VALUES(valueA, valueB)</literal>). Without this option the
+ column list will be omitted.
+ </para>
+
+ <para>
+ <guilabel>Comment</guilabel> writes additional backup
+ information to the backup file in the form of SQL comments.
+ </para>
+
+ <para>
+ <guilabel>Fully Qualified Identifiers</guilabel> causes
+ &administrator; to write statements in the format,
+ <literal>schema_name.table_name</literal>, instead of writing
+ only the object name. (Under Linux this check box is labeled
+ <guilabel>Don't write full path</guilabel>.) Don't check this
+ option if you plan to restore your database objects to a
+ different database.
+ </para>
+
+ <para>
+ <guilabel>Compatibility mode</guilabel> creates backup files
+ that are compatible with older versions of &administrator;.
+ </para>
+
+ <para>
+ <guilabel>ANSI Quotes</guilabel> will cause all table and
+ database names to be quoted with ANSI style double quotes
+ instead of backticks.
+ </para>
+
+ <para>
+ <guilabel>Disable keys</guilabel> will add an <literal>ALTER
+ TABLE ... DISABLE KEYS</literal> statement to the backup file
+ before the <literal>INSERT</literal> statements that populate
+ the tables. This allows for faster recovery by loading all data
+ before rebuilding the index information.
+ </para>
+
+ </section>
+
+<!-- END OUTPUT OPTIONS -->
+
+ </section>
+
+<!-- END ADVANCED OPTIONS -->
+
+ <section id="mysql-administrator-backup-schedule">
+
+ <title>Schedule</title>
+
+ <para>
+ The <guilabel>Schedule</guilabel> tab. is used to execute backup
+ operations on a daily, weekly, or monthly basis.
+ </para>
+
+ <para>
+ In order to run a scheduled backup, you must be using a stored
+ connection. Without one you will see the following warning:
+ </para>
+
+<programlisting>
+A scheduled backup requires a stored connection. You are currently
+connected without using such a stored connection. Please use the connection
+manager to create one and use it then for the login.
+</programlisting>
+
+ <para>
+ For instructions on creating a stored connection see,
+ <xref linkend="mysql-administrator-starting-connection"/>.
+ </para>
+
+ <para>
+ To enable scheduling for your backup project, check the
+ <guilabel>Schedule this backup project</guilabel> checkbox. You
+ will need to choose a target directory for the backup files and
+ also a name for them. You can browse for a target directory by
+ clicking the <guibutton>…</guibutton> button.
+ </para>
+
+ <para>
+ If you have enabled the <guilabel>Add Date/Time to Backup
+ Files</guilabel> option in the <literal>Administrator
+ Options</literal> dialog, then the date and time of the backup
+ will be appended to the file name automatically. See
+ <xref linkend="mysql-gui-options-administrator-backup" /> for more
+ information on setting this option.
+ </para>
+
+ <para>
+ Once you have decided on a file name and target directory, you can
+ set the interval of the backup operation. Regardless of your
+ choice of daily, weekly, or monthly backups, you can set the time
+ that the backup will occur by setting the
+ <guilabel>Time</guilabel> option. Set the backup time in a 24 hour
+ format (i.e. 23:30).
+ </para>
+
+ <para>
+ When you select the <guilabel>Execute Backup Weekly</guilabel>
+ option, a set of check boxes representing the days of the week
+ will be displayed. Check the boxes corresponding to the days when
+ you want to perform backups.
+ </para>
+
+ <para>
+ When you select the <literal>Execute backup monthly</literal>
+ option, a list of dates will appear, allowing you to choose the
+ day of the month for backups.
+ </para>
+
+ <para>
+ Click the <guibutton>Save Project</guibutton> button to save your
+ preferences. After your project is saved it will be executed at
+ the next scheduled interval. To run the backup operation
+ immediately click the <guibutton>Execute Backup Now</guibutton>
+ button.
+ </para>
+
+ </section>
+
+<!-- END SCHEDULE -->
+
+</chapter>
Added: trunk/th/administrator/catalogs.xml
===================================================================
--- trunk/th/administrator/catalogs.xml (rev 0)
+++ trunk/th/administrator/catalogs.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 223, Lines Deleted: 0; 8230 bytes
@@ -0,0 +1,223 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-catalogs">
+
+ <title>Catalogs</title>
+
+ <section id="mysql-administrator-catalogs-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ This section deals with viewing catalogs, schemata, tables and
+ their properties, creating databases, and performing a number of
+ operations on tables. Existing catalogs and schemata are listed in
+ the lower left area of the
+ <link linkend="mysql-administrator-sidebar">sidebar</link>.
+ </para>
+
+ <para>
+ If there are many schemata on your MySQL server, the field with
+ the magnifying glass icon may be handy for filtering the schemata
+ you are looking for. Typing in <literal>t</literal> or
+ <literal>T</literal>, for example, will set the filter to schemata
+ whose names begin with a <literal>t</literal>. The filter works in
+ a case-insensitive fashion.
+ </para>
+
+ <para>
+ You may also filter schemata using the wild card
+ <literal>?</literal> to stand in for any single character and
+ <literal>*</literal> for zero to any number of characters. For
+ example the string <literal>*boo?*</literal> will find schemata
+ with the names <literal>books, coursebooks</literal> and
+ <literal>bookings</literal>.
+ </para>
+
+ <para>
+ Select the database that you wish to view. Right click on any
+ database and choose the <guimenu>Refresh Schemata List</guimenu>
+ option to refresh the database list. Clicking on a database will
+ cause the <guilabel>Schema Tables</guilabel> and <guilabel>Schema
+ Indices</guilabel> tabs to be populated with the tables and
+ indexes of the selected database.
+ </para>
+
+ <para>
+ To create a new database, right click on an existing database and
+ choose the <guimenu>Create New Schema</guimenu> option.
+ </para>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-catalogs-schema-tables">
+
+ <title>Schema Tables</title>
+
+ <para>
+ The <guilabel>Schema Tables</guilabel> tab lists the different
+ tables in the selected database, along with the rowcount, data
+ length, and index length for those tables. For MyISAM tables, you
+ also find the date and time when the table was last modified,
+ under <guilabel>Update Time</guilabel>. You can update the list of
+ tables by pressing the <guibutton>Refresh</guibutton> button.
+ </para>
+
+ <para>
+ The tables are ordered by table name initially, but you may change
+ that sorting by clicking on the appropriate headings
+ (<guilabel>Type</guilabel>, <guilabel>Row Format</guilabel>,
+ etc.).
+ </para>
+
+ <para>
+ To drop a table, right click on the table and choose the
+ <guimenu>Drop Table</guimenu> option from the pop-up menu. To
+ create a table you can either click the <guibutton>Create
+ Table</guibutton> button at the bottom of the window, or
+ right-click on a table and choose the <guimenu>Create
+ Table</guimenu> option from the pop-up menu.
+ </para>
+
+ <para>
+ To edit a table's columns and indexes, right-click on the desired
+ table and choose the <guimenu>Edit Table</guimenu> option from the
+ pop-up menu. This will launch the MySQL Table Editor, which you
+ can use to modify the table. For more information see
+ <xref linkend="gui-table-editor" /> .
+ </para>
+
+ <para>
+ To edit a table's actual data, right click on the table and choose
+ the <guimenu>Edit Table Data</guimenu> option. This will launch
+ the MySQL Query Browser and load the table's data into the result
+ area of the MySQL Query Browser.
+ </para>
+
+ <para>
+ To perform operations on multiple tables select more than one
+ table. For the selected tables, you can perform operations by
+ either clicking the <guibutton>Maintenance</guibutton> button at
+ the bottom of the table list or by right clicking on one of the
+ selected tables and choosing from the
+ <guimenu>Maintenance</guimenu> sub-menu of the pop-up menu:
+ </para>
+
+ <para>
+ The available options are:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guimenu>Optimize Table</guimenu>: This corresponds to the
+ <literal>OPTIMIZE TABLE</literal> SQL command and should be
+ used if you have deleted a large part of a table or if you
+ have made many changes to a table with variable-length rows
+ (tables that have <literal>VARCHAR</literal>,
+ <literal>BLOB</literal>, or <literal>TEXT</literal> columns).
+ Deleted records are maintained in a linked list and subsequent
+ <literal>INSERT</literal> operations reuse old record
+ positions. You can use this command to reclaim the unused
+ space and to defragment the datafile. Note that table
+ optimization works for MyISAM and BDB tables only. For more
+ information see <xref linkend="optimize-table"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Check Table</guimenu>: This corresponds to the
+ <literal>CHECK TABLE</literal> SQL command and is used to
+ diagnose table problems. For more information see
+ <xref linkend="check-table"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Repair Table</guimenu>: This corresponds to the
+ <literal>REPAIR TABLE</literal> SQL command and should be used
+ in case of table problems. Note that this command works for
+ MyISAM tables only. For more information see
+ <xref linkend="repair-table"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Clicking on a table name will display its properties in the
+ details area when the details area is active. To display the
+ details area, click the <guibutton>Details >></guibutton> button.
+ </para>
+
+ <section
+ id="mysql-administrator-catalogs-schema-tables-table-status">
+
+ <title>Table Status</title>
+
+ <para>
+ In this tab, you find detailed information about the selected
+ table. This information could also be retrieved by issuing a
+ <literal>SHOW TABLE STATUS LIKE 'tbl'</literal> SQL command. For
+ more information see <xref linkend="show-table-status"/>.
+ </para>
+
+ </section>
+
+<!-- Table Status -->
+
+ <section id="mysql-administrator-catalogs-schema-tables-row-status">
+
+ <title>Row Status</title>
+
+ <para>
+ In this tab, you find detailed information about the rows of the
+ selected table. This information can also be retrieved by
+ issuing a <literal>SHOW TABLE STATUS LIKE 'tbl'</literal> SQL
+ command. For more information see
+ <xref linkend="show-table-status"/>.
+ </para>
+
+ </section>
+
+<!-- Row Status -->
+
+ </section>
+
+<!-- Schema Tables -->
+
+ <section id="mysql-administrator-catalogs-indexes">
+
+ <title>Schema Indexes</title>
+
+ <para>
+ The <guilabel>Schema Indices</guilabel> tab lists the indexes of
+ the selected database. Besides the index names and the table the
+ index belongs to, you can also see the index type, whether values
+ are unique, and whether NULL values are allowed. You can also get
+ this information by issuing a <literal>SHOW INDEX</literal> SQL
+ command in a command-line client (see
+ <xref linkend="show-databases"/>). For more information about
+ indexes, see <xref linkend="indexes"/>.
+ </para>
+
+ <para>
+ To see the columns that form a given index, double click on the
+ index.
+ </para>
+
+ </section>
+
+<!-- END INDICES -->
+
+</chapter>
Added: trunk/th/administrator/chapter-options-administrator.xml
===================================================================
--- trunk/th/administrator/chapter-options-administrator.xml (rev 0)
+++ trunk/th/administrator/chapter-options-administrator.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 146, Lines Deleted: 0; 5149 bytes
@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<section id="mysql-gui-options-administrator">
+
+ <title>Administrator</title>
+
+ <para>
+ The <literal>Administrator</literal> section allows you to specify
+ options that affect the behavior of the &administrator;. The
+ <literal>Administrator</literal> section is divided into four
+ sub-sections that will be discussed further in the sections that
+ follow.
+ </para>
+
+ <section id="mysql-gui-options-administrator-user-administration">
+
+ <title>User Administration</title>
+
+ <para>
+ These options affect the interface of the
+ <link linkend="mysql-administrator-user-administration">User
+ Administration</link> section of &administrator;.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Show Global Privileges</guilabel>: If checked, the
+ <link linkend="mysql-administrator-user-administration-global-privileges">Global
+ Privileges</link> tab will be visible in the
+ <link linkend="mysql-administrator-user-administration">User
+ Administration</link> section. In that tab, you can grant
+ users global privileges (as opposed to privileges on a
+ database, table, or column level only). This may affect
+ security. See <xref linkend="privilege-system"/>. If
+ unchecked, the
+ <link linkend="mysql-administrator-user-administration-global-privileges">Global
+ Privileges</link> tab will not be visible in the
+ <link linkend="mysql-administrator-user-administration">User
+ Administration</link> section.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Show Table/Column Privileges</guilabel>: In most
+ situations, it is sufficient to grant either global or
+ database privileges for users. You can hide the
+ <link linkend="mysql-administrator-user-administration-table-column-privileges">Table/Column
+ Privileges</link> tab in the
+ <link linkend="mysql-administrator-user-administration">User
+ Administration</link> section by enabling this checkbox.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- END USER ADMINISTRATION -->
+
+ <section id="mysql-gui-options-administrator-health-graphs">
+
+ <title>Health Graphs</title>
+
+ <para>
+ These options affect the appearance of the
+ <link linkend="mysql-administrator-health">Health Graphs</link>
+ section of &administrator;.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Use Peak Level Indicator</guilabel>: This will
+ display a thin yellow line on the health graphs indicating the
+ highest value recorded by the graph.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Reset Peak Level after a number of ticks</guilabel>:
+ If this box is not checked, the <literal>Peak Level
+ Indicator</literal> will be permanently positioned at the
+ highest value ever recorded on the health graph. With this box
+ checked, the <literal>Peak Value Indicator</literal> will be
+ reset after a period of time indicated by the <guilabel>Time
+ after the Peak level resets</guilabel> option. Use this option
+ if you would like to know the peak level over an interval
+ rather than the peak level overall.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Ticks after the Peak level resets</guilabel>: When
+ the <guilabel>Reset Peak Level after a number of
+ ticks</guilabel> option is set, this determines the amount of
+ time (in ticks) that will pass before the <literal>Peak Level
+ Indicator</literal> will be reset.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- END HEALTH GRAPHS -->
+
+ <section id="mysql-gui-options-administrator-backup">
+
+ <title>Backup</title>
+
+ <para>
+ The backup options configure how &administrator; performs backup
+ operations.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Add Date/Time to Backup Files</guilabel>: This
+ determines whether the date and time of the backup operation
+ are added to the name of the backup file. See
+ <link linkend="mysql-administrator-backup">the backup
+ section</link> for more information.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- END BACKUP -->
+
+</section>
+<!-- END ADMINISTRATOR SECTION-->
Added: trunk/th/administrator/connection-dialog.xml
===================================================================
--- trunk/th/administrator/connection-dialog.xml (rev 0)
+++ trunk/th/administrator/connection-dialog.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 328, Lines Deleted: 0; 11617 bytes
@@ -0,0 +1,328 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<!-- Installing &administrator; -->
+<chapter id="mysql-administrator-starting">
+
+ <title>Connection Dialog</title>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-starting-connection">
+
+ <title>Connection Dialog</title>
+
+ <para>
+ Once &administrator; has been started, it displays a connection
+ dialog box. Specify the MySQL server you would like to connect to,
+ the necessary credentials, and both the host and port. You may
+ also specify a number of other options, if required.
+ </para>
+
+ <para>
+ As an alternative to connecting to a running MySQL server, you can
+ run &administrator; in Configure-service mode. For information on
+ this topic see
+ <xref linkend="mysql-administrator-starting-configure-service"/>.
+ </para>
+
+ <figure>
+ <title>Connection dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/connection.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Connection dialog</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ Note that &administrator; will not work with MySQL servers prior
+ to version 4.0. If you try to connect to an older server, an error
+ message will be displayed.
+ </para>
+
+ <para>
+ If the server connection is successfully established, the values
+ in the fields of the connection dialog will be saved for future
+ connections. For more information on this topic see
+ <xref linkend="mysql-gui-appendix-store-connections"/>. However,
+ for security reasons the password is not stored along with the
+ other options unless you explicitly specify otherwise. For
+ instructions on storing the password see
+ <xref linkend="mysql-gui-options-general-options"/>.
+ </para>
+
+ <para>
+ You can change any of the values in the connection profiles by
+ overwriting the existing values with new ones. Similarly, if you
+ select another connection profile, you can change any of its
+ values. If a successful connection to the MySQL server is
+ established, clicking the <guibutton>OK</guibutton> button after
+ changing a profile's values, permanently saves the changes.
+ However, the preferred method for changing a profile is to click
+ the <guibutton>...</guibutton> button next to the
+ <guilabel>Connection</guilabel> drop-down box. That brings up an
+ <guilabel>Options</guilabel> dialog window that has a
+ <guilabel>Connections</guilabel> section for modifying connection
+ profiles. You can find the values you can set in the Connection
+ dialog window in the description of the
+ <guilabel>Connections</guilabel> section of the
+ <literal>Options</literal> dialog (see
+ <xref linkend="mysql-gui-options-connections"/>).
+ </para>
+
+ <para>
+ The nature of the connection to the MySQL server varies depending
+ upon the value specified in the <guilabel>Server Host:</guilabel>
+ text box.
+ </para>
+
+ <para>
+ Under Linux and Mac OS X the connection to the MySQL server will
+ be a socket connection if <quote>localhost</quote> is used in the
+ <guilabel>Server Host:</guilabel> text box. Specifying
+ <literal>127.0.0.1</literal>, the actual IP address that hosts the
+ MySQL server, or the host name results in a TCP connection.
+ </para>
+
+ <para>
+ Under Windows, the connection is always a TCP connection unless
+ you connect using named pipes. This is discussed in the following
+ section.
+ </para>
+
+ <section id="administrator-advanced-connection-options">
+
+ <title>Advanced Options</title>
+
+ <para>
+ To set advanced connection options, click the
+ <guibutton>Details</guibutton> button and check the desired
+ options:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>Use compression protocol</literal> - Use
+ compression when communicating with the MySQL server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Use ANSI quotes to quote identifiers</literal> -
+ enclose all object names in double-quotes instead of
+ back-ticks.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Windows Only:</emphasis> <literal>Use
+ named pipe (localhost only)</literal> is equivalent to
+ starting the client from the command line specifying the
+ <option>--protocol</option>=<replaceable>pipe</replaceable>
+ option.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Unix Only:</emphasis> <literal>Connect
+ using a socket file</literal> is equivalent to starting the
+ client from the command line specifying the
+ <option>--protocol</option>=<replaceable>socket</replaceable>
+ option.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ If you have difficulties connecting, please see the
+ <link linkend="mysql-gui-appendix-troubleshooting-connection-errors">Troubleshooting
+ Connection Errors</link> section in the
+ <link linkend="mysql-gui-appendix-troubleshooting">Troubleshooting
+ Application Errors</link> appendix.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- Connection Dialog -->
+
+ <section id="mysql-administrator-starting-configure-service">
+
+ <title>Configure-service Mode</title>
+
+ <para>
+ Normally, you will use &administrator; to connect to a running
+ MySQL server. This is done by starting the program and specifying
+ in the
+ <link linkend="mysql-administrator-starting-connection">Connection</link>
+ dialog which server to connect to.
+ </para>
+
+ <para>
+ Alternatively, you can run &administrator; in configure-service
+ mode. This is useful in the following cases:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ When you want to start a MySQL server from within MySQL
+ Administrator. Obviously, you cannot connect to a server that
+ is not running, so you will have to use the configure-service
+ mode to start that server. Note that you can only start
+ servers on the same machine where &administrator; is running
+ (that is on the local host).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When you have multiple servers running on your machine. When
+ running in normal mode on Windows, MySQL Administrator only
+ allows you to configure the Windows service that is listed
+ first in the Microsoft Management Console window. This means
+ that if you have more than one Windows service, you can only
+ configure the first one of those, no matter which server you
+ connect to. If you want to configure a service other than the
+ first service, you will have to run &administrator; in
+ configure-service mode.
+
+ <remark>
+ [PL] Asked Alfredo if this is still true.
+ </remark>
+
+ For more information on this topic see
+ <xref linkend="multiple-servers"/>.
+ </para>
+
+ <note>
+ <para>
+ The preceding applies only to &administrator; when running
+ on Windows.
+ </para>
+ </note>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ To start &administrator; in configure-service mode, hold down the
+ <keycap>CTRL</keycap> key in the
+ <link linkend="mysql-administrator-starting-connection">Connection</link>
+ dialog. The <guibutton>Cancel</guibutton> button will toggle to
+ <guibutton>Skip</guibutton> when the <keycap>CTRL</keycap> key is
+ pressed.
+ </para>
+
+ <figure>
+ <title>Switching to configure-service mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/configure-service-mode-connection.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Switching to configure-service mode</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ Clicking on the <guibutton>Skip</guibutton> button will skip
+ normal mode and start &administrator; in configure-service mode.
+ You should see something similar to the following.
+ </para>
+
+ <figure>
+ <title>Configure-service mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/configure-service-mode-window.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Configure-service mode</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ Under <guilabel>Installed Services</guilabel> in the
+ <link linkend="mysql-administrator-sidebar">sidebar</link>, you
+ can select the service that you wish to configure, or the server
+ that you want to stop or start. Only servers that have been
+ installed using the Windows installer will appear here.
+ </para>
+
+ <note>
+ <para>
+ <guilabel>Installed Services</guilabel> is only displayed under
+ Windows.
+ </para>
+ </note>
+
+ <para>
+ In configure-service mode, only the following sidebar options are
+ available:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The
+ <link linkend="mysql-administrator-service-control">Service
+ Control</link> section allows you to start and stop a MySQL
+ server, and to configure the Windows service managing that
+ server. Servers are stopped using the
+ <command>mysqladmin</command> utility. This program is part of
+ the default MySQL installation but if you have removed it you
+ will not be able to stop a server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link> section allows you to set variables for
+ server startup.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The
+ <link linkend="mysql-administrator-server-logs-introduction">Server
+ Logs</link> section allows you to examine the server logs.
+ Note: You do not need to connect in configure-service mode to
+ examine the server logs. This option is available when you
+ connect to a specific server instance.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ All of these sections are described in what follows.
+ </para>
+
+ </section>
+
+<!-- Configure-service Mode -->
+
+</chapter>
Property changes on: trunk/th/administrator/connection-dialog.xml
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/th/administrator/health.xml
===================================================================
--- trunk/th/administrator/health.xml (rev 0)
+++ trunk/th/administrator/health.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 371, Lines Deleted: 0; 14302 bytes
@@ -0,0 +1,371 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-health">
+
+ <title>Health</title>
+
+ <section id="mysql-administrator-health-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The <literal>Health</literal> section of &administrator; shows you
+ how to graphically monitor the real-time status of your MySQL
+ server. A selection of pre-made status graphs are available, and
+ you can easily create your own status graphs and organize them
+ into custom pages and groups.
+ </para>
+
+ <para>
+ The default graphs provide graphical information about the MySQL
+ server's current performance, load, and memory usage. Additional
+ pages list all server variables, with tabs for memory health,
+ status variables and system variables. Note that clicking on the
+ status pages will open an additional connection to the MySQL
+ server, which you can see when viewing threads and users in the
+ <link linkend="mysql-administrator-server-connections">Server
+ Connections</link> section.
+ </para>
+
+ <para>
+ We'll begin by covering the different pre-made status graphs, and
+ then describe how to create your own status graphs. Finally we'll
+ describe the pages in the <literal>Health</literal> section
+ dedicated to the various status and system variables.
+ </para>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-health-connection-health">
+
+ <title>Connection Health</title>
+
+ <para>
+ This tab provides information about connections to the MySQL
+ server. The following three pre-made graphs are displayed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Connection Usage</guilabel>: Displays a percentage
+ of the maximum number of simultaneous clients allowed
+ (<literal>threads connected</literal> /
+ <literal>max_connections</literal>). If this value gets close
+ to 100%, it could indicate that you should increase the value
+ of max_connections, which you can do in the
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link> section. The maximum number of connections
+ since &administrator; was loaded is also shown. For more
+ information on server connections, see
+ <xref linkend="show-variables"/>, and
+ <xref linkend="too-many-connections"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Traffic</guilabel>: This is a representation of the
+ <literal>bytes_sent</literal> status variable. This does not
+ represent total bytes sent since server startup, but instead
+ represents the current number of bytes sent (the
+ <literal>bytes_sent</literal> variable is a cumulative total).
+ The initial maximum value of the graph is 102400, this maximum
+ value will be automatically increased as needed.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Number of SQL Queries</guilabel>: This is a
+ representation os the <literal>com_select</literal> status
+ variable. This does not represent total queries since server
+ startup, but instead represents the current number of queries
+ (the <literal>com_select</literal> variable is a cumulative
+ total). The initial maximum value of the graph is 10, this
+ maximum value will be automatically increased as needed.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- END CONNECTION HEALTH -->
+
+ <section id="mysql-administrator-health-memory-health">
+
+ <title>Memory Health</title>
+
+ <para>
+ This tab provides information about memory caches that affect the
+ performance of the MySQL server. For each cache, there is a
+ display that shows the current hit rate or usage of the cache, and
+ a display that shows the hit rate or usage for the last few
+ minutes.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Query Cache Hitrate</guilabel>: When in use, the
+ query cache of the MySQL server stores the text of a
+ <literal>SELECT</literal> query together with the
+ corresponding result that was sent to the client. If an
+ identical query is later received, the server will retrieve
+ the results from the query cache rather than parsing and
+ executing the same query again. The hit rate indicates the
+ ratio of queries that were cached and queries that were not
+ cached. The higher the hit rate, the better the performance of
+ the server regarding <literal>SELECT</literal> queries. See
+ <xref linkend="query-cache"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Key Efficiency</guilabel>: The horizontal bar graph
+ indicates how much of the allocated key buffer is in use. If a
+ fairly large percentage of the key buffer is in use you may
+ wish to increase the <literal>key_cache_size</literal> setting
+ in the
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link> section. The line graph is an indication of
+ the number of <literal>key_read_requests</literal> that
+ resulted in actual <literal>key_reads</literal>. The higher
+ the hit rate the more effective your key buffer is. A low hit
+ rate can indicate that you need to increase the size of your
+ keycache.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- END MEMORY HEALTH -->
+
+ <section id="mysql-administrator-health-creating-graphs">
+
+ <title>Creating Custom Health Graphs</title>
+
+ <para>
+ While the pre-made status graphs can provide you with information
+ of the current state of your MySQL server, there may be
+ additionally information that you wish to visually track. The
+ &administrator; <literal>Health</literal> section allows you to
+ add additional tabs and graphs to track any information that is
+ contained within the
+ <link linkend="mysql-administrator-health-status-variables">Status
+ Variables</link>.
+ </para>
+
+ <para>
+ The first step in creating custom health graphs is to create a new
+ page in the <literal>Health</literal> section to store your
+ graphs. To create a new page right click anywhere in the working
+ area and choose the <guimenu>Add a Page</guimenu> option. You will
+ be prompted for a page name and description and a new page will be
+ created.
+ </para>
+
+ <para>
+ Once you have created a new page, you will need to create a group.
+ All graphs are organized into groups. For example, the
+ <literal>Key buffer usage</literal> and <literal>Key buffer hit
+ rate</literal> graphs are both members of the group titled
+ <literal>Key Efficiency</literal>. To create a group, right click
+ within your newly created page and choose the <guimenu>Add a
+ Group</guimenu> option.
+ </para>
+
+ <para>
+ To create a custom graph, right click within a group and choose
+ the <guimenu>Add a graph</guimenu> option. The following dialog
+ will appear:
+ </para>
+
+ <figure>
+ <title>The Graph Settings dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/graph-settings.png" lang="en" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">The Graph Settings dialog</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ The <guilabel>Line-Graph</guilabel> is appropriate for showing
+ trends over time, while the <guilabel>Bar-Graph</guilabel> option
+ will be more appropriate for showing percentage information. If
+ you choose to create a bar-graph, you will need to choose a
+ caption for your graph. Captions are not allowed for line-graphs.
+ </para>
+
+ <para>
+ The data on your graph is set using the <literal>Value
+ Formula</literal>. You can create a formula using any of the
+ variables available in the
+ <link linkend="mysql-administrator-health-status-variables">Status
+ Variables</link> and
+ <link linkend="mysql-administrator-health-system-variables">System
+ Variables</link> tabs. To use the value of a variable, wrap the
+ variable name in square brackets (i.e.
+ <literal>[com_select]</literal>), if you want the relative value
+ of the variable prepend the square brackets with a
+ <literal>^</literal> character.
+ </para>
+
+ <para>
+ For example, if we wanted to graph the percentage of temporary
+ tables that were created on disk we could use the following
+ formula:
+ </para>
+
+<programlisting>
+ [created_tmp_disk_tables] / [created_tmp_tables]
+ </programlisting>
+
+ <para>
+ If we wanted to track the number of temporary tables created on a
+ continuous basis, we could use the following as our formula:
+ </para>
+
+<programlisting>
+ ^[created_tmp_tables]
+ </programlisting>
+
+ <para>
+ After creating your formula, select the <guilabel>Value
+ Unit</guilabel> that best represents your data. You can choose
+ from <literal>Percentage</literal>, <literal>Count</literal>,
+ <literal>Byte</literal>, and <literal>Seconds</literal>. In our
+ examples we would use <literal>Percentage</literal> for the first
+ example, and <literal>Count</literal> for the second. You can also
+ assign a caption to the value.
+ </para>
+
+ <para>
+ Once your formula is assigned you should configure the
+ <literal>Max. Value</literal> and <literal>Min. Value</literal>
+ for the graph, so that your data is spread evenly across your
+ graph. You can set arbitrary values based on your estimates of how
+ large the values will grow, and check the <guimenu>Autoextend Max.
+ Value</guimenu> option to allow &administrator; to automatically
+ increase the <literal>Max Value</literal> setting automatically to
+ prevent your data from extending off of your graph.
+ </para>
+
+ <para>
+ You can also set the <literal>Max. Value</literal> option by way
+ of a formula assigned in the <guilabel>Max Formula</guilabel>
+ field. The same syntax applies in this field as applies in the
+ <guilabel>Value Formula</guilabel> field. For example, if you were
+ creating a bar graph tracking the number of temporary disk tables
+ created, you could use
+ <literal>[created_tmp_disk_tables]</literal> as the
+ <guilabel>Value Formula</guilabel> and
+ <literal>[created_tmp_tables]</literal> as the <guilabel>Max.
+ Formula</guilabel>.
+ </para>
+
+ </section>
+
+<!-- END CREATING GRAPHS -->
+
+ <section id="mysql-administrator-health-status-variables">
+
+ <title>Status Variables</title>
+
+ <para>
+ This tab provides information about the status variables of the
+ MySQL server. In the left box of the working area, you find
+ categories and subcategories. Double click on a category name to
+ expand or collapse its subcategories.
+ </para>
+
+ <para>
+ For each category, and each subcategory, the status variables are
+ listed in the right box of the working area, together with their
+ values, and with a short explanation. See
+ <xref linkend="show-status"/>, for more detail on server status
+ variables.
+ </para>
+
+ <para>
+ Use the <guibutton>Refresh</guibutton> button to make
+ &administrator; retrieve the variables and their values once
+ again.
+ </para>
+
+ <para>
+ Right clicking in the right box allows you to copy variables to
+ the clipboard.
+ </para>
+
+ </section>
+
+<!-- Status Variables -->
+
+ <section id="mysql-administrator-health-system-variables">
+
+ <title>System Variables</title>
+
+ <para>
+ This tab provides information about the system variables of the
+ MySQL server. In the left box of the working area, you can find
+ categories and subcategories. Double click on a category name to
+ expand or collapse its subcategories.
+ </para>
+
+ <para>
+ For each category, and each subcategory, the system variables are
+ listed in the right box of the working area, together with their
+ values and a short explanation. See
+ <xref linkend="show-variables"/>, for more information on system
+ variables.
+ </para>
+
+ <para>
+ System variables that can be set at runtime are marked as
+ editable, that is they are prefixed with an icon different from
+ the variables that cannot be set at runtime. Double clicking on
+ editable variables will open a dialog box allowing you to specify
+ another value for the variable. The changes you make will take
+ effect as soon as you confirm the changes by clicking the
+ <guibutton>OK</guibutton> button. Click
+ <guibutton>Abort</guibutton> if you want to keep the current
+ value. Changes made in this manner will only persist until the
+ server is restarted, after which the server will revert to it's
+ startup settings. In &administrator;, system variables are set on
+ a global level only. Note that you need appropriate privileges to
+ change variables globally. See <xref linkend="set-option"/>.
+ </para>
+
+ <para>
+ Use the <guibutton>Refresh</guibutton> button to make MySQL
+ Administrator retrieve the variables and their values once again.
+ </para>
+
+ <para>
+ Right clicking in the right box allows you to copy variables to
+ the clipboard.
+ </para>
+
+ </section>
+
+<!-- END SYSTEM VARIABLES -->
+
+</chapter>
Added: trunk/th/administrator/images/published/README
===================================================================
--- trunk/th/administrator/images/published/README (rev 0)
+++ trunk/th/administrator/images/published/README 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 33, Lines Deleted: 0; 1498 bytes
@@ -0,0 +1,33 @@
+Image directories contain all images (screen shots, diagrams, etc.)
+of a particular document (or, in the case of "common" directories,
+of a set of documents).
+
+The "source" subdirectories contain source files that are not meant to
+be used for publication, while "published" contain files that are meant
+to be published.
+
+For non-English (translated) documents the setup is identical.
+
+The following demonstrates how this is organised, and also indicates
+which types of files are supposed to go where.
+
+ .../
+ |images/
+ | |source/
+ | | *.svg
+ | | *.dia
+ | | *.graffle
+ | | *.xmi(.gz)
+ | |
+ | |published/
+ | *.png (screen shots)
+ | *.png (created from SVG)
+ | *.png (created from XMI)
+ | *.png (created from DIA)
+ |
+ |cy/ (Welsh translation)
+ |
+ |images/
+ |... (subdirectories as above)
+
+Last modified: 2007-06-25 by Stefan Hinz, stefan@stripped.
Property changes on: trunk/th/administrator/images/published/README
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/th/administrator/images/published/backup-completed.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 377 bytes
Added: trunk/th/administrator/images/published/backup-content.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 373 bytes
Added: trunk/th/administrator/images/published/backup-progress.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 375 bytes
Added: trunk/th/administrator/images/published/configure-service-mode-connection.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 411 bytes
Added: trunk/th/administrator/images/published/configure-service-mode-window.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 403 bytes
Added: trunk/th/administrator/images/published/connection.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 365 bytes
Added: trunk/th/administrator/images/published/error.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 355 bytes
Added: trunk/th/administrator/images/published/graph-settings.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 373 bytes
Added: trunk/th/administrator/images/published/mainwindow.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 365 bytes
Added: trunk/th/administrator/images/published/marked-area.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 367 bytes
Added: trunk/th/administrator/images/published/options-connections.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 383 bytes
Added: trunk/th/administrator/images/published/options-general-options.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 391 bytes
Added: trunk/th/administrator/images/published/replication.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 367 bytes
Added: trunk/th/administrator/images/published/restore-content.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 375 bytes
Added: trunk/th/administrator/images/published/server-logs-general-log.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 391 bytes
Added: trunk/th/administrator/images/published/system-tray.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 367 bytes
Added: trunk/th/administrator/images/published/user-accounts.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 371 bytes
Added: trunk/th/administrator/images/published/user-information.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 377 bytes
Added: trunk/th/administrator/introduction.xml
===================================================================
--- trunk/th/administrator/introduction.xml (rev 0)
+++ trunk/th/administrator/introduction.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 66, Lines Deleted: 0; 2187 bytes
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-introduction">
+
+ <title>Introduction to &administrator;</title>
+
+ <para>
+ &administrator; is a program for performing administrative
+ operations, such as configuring, monitoring and starting and
+ stopping a MySQL server, managing users and connections, performing
+ backups, and a number of other administrative tasks.
+ </para>
+
+ <para>
+ Most tasks can be performed using a command-line client such as
+ <xref linkend="mysqladmin"/>, or
+ <link linkend="mysql"><command>mysql</command></link>, but
+ &administrator; has the following advantages:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Its graphical user interface makes it more intuitive.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It provides a better overview of the settings that are crucial
+ for the performance, reliability, and security of your MySQL
+ servers.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It displays performance indicators graphically, thus making it
+ easier to determine and tune server settings.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ &administrator; is designed to work with MySQL versions 4.0 and
+ higher.
+ </para>
+
+ <para>
+ &administrator; is, to a large extent, the result of feedback MySQL
+ AB has received from many users over a period of several years.
+ However, if you find it's lacking some feature important to you, or
+ if you discover a bug, please use our
+ <ulink
+ url="http://bugs.mysql.com">MySQL Bug System</ulink>
+ to request features or report problems.
+ </para>
+
+</chapter>
Added: trunk/th/administrator/legalnotice.en.xml
===================================================================
--- trunk/th/administrator/legalnotice.en.xml (rev 0)
+++ trunk/th/administrator/legalnotice.en.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 67, Lines Deleted: 0; 3112 bytes
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+<legalnotice>
+
+<!--
+ The role attribute for each top-level legalnotice element determines
+ the context in which the element is used: 1) no role attribute: part
+ of the default legalnotice, used for regular documentation that is
+ not released under GPL; 2) role = legalnotice-gpl: for manpage
+ legalnotices, which are released under GPL; 3) role =
+ legalnotice-all: included in legalnotice for all documentation.
+-->
+
+ <para>
+ Copyright 2004-2007 MySQL AB
+ </para>
+
+ <para>
+ This documentation is NOT distributed under a GPL license. Use of
+ this documentation is subject to the following terms: You may create
+ a printed copy of this documentation solely for your own personal
+ use. Conversion to other formats is allowed as long as the actual
+ content is not altered or edited in any way. You shall not publish
+ or distribute this documentation in any form or on any media, except
+ if you distribute the documentation in a manner similar to how MySQL
+ disseminates it (that is, electronically for download on a Web site
+ with the software) or on a CD-ROM or similar medium, provided
+ however that the documentation is disseminated together with the
+ software on the same medium. Any other use, such as any
+ dissemination of printed copies or use of this documentation, in
+ whole or in part, in another publication, requires the prior written
+ consent from an authorized representative of MySQL AB. MySQL AB
+ reserves any and all rights to this documentation not expressly
+ granted above.
+ </para>
+
+ <para role="legalnotice-gpl">
+ Copyright 2007 MySQL AB
+ </para>
+
+ <para role="legalnotice-gpl">
+ This documentation is free software; you can redistribute it and/or
+ modify it under the terms of the GNU General Public License as
+ published by the Free Software Foundation; version 2 of the License.
+ </para>
+
+ <para role="legalnotice-gpl">
+ This documentation 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 GNU
+ General Public License for more details.
+ </para>
+
+ <para role="legalnotice-gpl">
+ You should have received a copy of the GNU General Public License
+ along with the program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+ 02110-1301 USA or see http://www.gnu.org/licenses/.
+ </para>
+
+ <para role="legalnotice-all">
+ Please email <email>docs@stripped</email> for more information or
+ if you are interested in doing a translation.
+ </para>
+
+</legalnotice>
Added: trunk/th/administrator/main-window.xml
===================================================================
--- trunk/th/administrator/main-window.xml (rev 0)
+++ trunk/th/administrator/main-window.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 450, Lines Deleted: 0; 12883 bytes
@@ -0,0 +1,450 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<!-- Starting &administrator; -->
+<chapter id="mysql-administrator-main-window">
+
+ <title>Main Window</title>
+
+ <section id="mysql-administrator-main-window-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ After you have successfully connected to your MySQL server, the
+ main window of &administrator; appears (see figure). The main
+ window contains a sidebar, a working area, and menus with
+ submenus.
+ </para>
+
+ <remark>
+ [SH] add annotations!)
+ </remark>
+
+ <figure>
+ <title>&administrator; main window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/mainwindow.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">&administrator; main window</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-sidebar">
+
+ <title>Sidebar</title>
+
+ <para>
+ The sidebar consists of the following options:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-server-information">Server
+ Information</link>: Information about the MySQL server you are
+ connected to, about &administrator; and the machine that it
+ runs on, and about your connection.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-service-control">Service
+ Control</link>: Start and stop the MySQL server. If
+ &administrator; is running on Windows and connected to a MySQL
+ server that is also running on Windows, you can configure the
+ MySQL service.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link>: Configure the startup variables for the
+ MySQL server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-server-connections">Server
+ Connections</link>: View or kill current connections to the
+ MySQL server (also called threads).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-user-administration">User
+ Administration</link>: Administer existing users, add new
+ users, and delete existing users.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-health">Health</link>:
+ Graphical displays of a number of usage or hit-rate values
+ that affect server performance, and a hierarchical view of
+ system and status variables.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-server-logs">Server
+ Logs</link>: View log file entries.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-backup">Backup</link>:
+ Plan and administer backup projects, select the databases to
+ be backed up, and start the backup process.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-restore">Restore</link>:
+ Restore databases from existing backups.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-replication-status">Replication
+ Status</link>: View information about replication master and
+ slave servers.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-catalogs">Catalogs</link>:
+ View information about databases, tables, columns, indexes,
+ and rows; optimize tables.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The following sections describe each of these in detail.
+ </para>
+
+ <para>
+ You can change the width of the sidebar in the main window by
+ dragging the separator between the sidebar and the working area.
+ To hide the sidebar completely, click on the marked area in the
+ separator (located in the vertical center of it). To make the
+ sidebar visible again, double click the marked area (which then
+ forms the left margin of the main window).
+ </para>
+
+ <figure>
+ <title>Marked area between sidebar and working area</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/marked-area.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Marked area between sidebar and working
+ area</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+<!-- Sidebar -->
+
+ <section id="mysql-administrator-working-area">
+
+ <title>Working Area</title>
+
+ <para>
+ While the
+ <link linkend="mysql-administrator-sidebar">sidebar</link> allows
+ you to select options, the working area displays information, or
+ fields, that pertain to the selected section. For some sections,
+ the working area is split into two or more tabs.
+ </para>
+
+ </section>
+
+<!-- Working Area -->
+
+ <section id="mysql-administrator-menus">
+
+ <title>Menus</title>
+
+ <section id="mysql-administrator-menus-file">
+
+ <title>File</title>
+
+ <section
+id="mysql-administrator-menus-file-new-instance-connection">
+
+ <title>New Instance Connection ...</title>
+
+ <para>
+ Opens the
+ <link linkend="mysql-administrator-starting-connection">Connection
+ dialog</link>, allowing you to open a connection to another
+ MySQL server. You may open an arbitrary number of connections.
+ MySQL Administrator opens a new main window for each
+ successfully established connection. Connections may be to the
+ same or different servers. Multiple connections may be opened
+ using the same profile or different profiles.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-file-manage-connections">
+
+ <title>Reconnect</title>
+
+ <para>
+ This option closes the current connection and opens the
+ <link linkend="mysql-gui-options">Options dialog</link>, with
+ the <link
+linkend="mysql-gui-options-connections">Connections
+ section</link> preselected.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-copy-active-page">
+
+ <title>Copy Active Page as Text ...</title>
+
+ <para>
+ This menu option copies the information displayed on the
+ <literal>Server Information</literal> page to the clipboard.
+ For more information about the <literal>Server
+ Information</literal> page see
+ <xref linkend="mysql-administrator-server-information" />.
+ </para>
+
+ <note>
+ <para>
+ <remark>
+ Not Linux. Mac OS X?
+ </remark>
+
+ This menu option is only available on Windows and only
+ copies the <literal>Server Information</literal> page.
+ </para>
+ </note>
+
+ </section>
+
+ <section id="mysql-administrator-menus-file-save-current-connection">
+
+ <title>Save current Connection ...</title>
+
+ <para>
+ Opens the <link linkend="mysql-gui-options">Options
+ dialog</link>, with the
+ <link
+linkend="mysql-gui-options-connections">Connections
+ section</link> preselected. Furthermore, a new connection
+ profile labeled <guilabel>New Connection</guilabel> is
+ created, and it is also preselected. The fields are filled
+ with the values of the most recent connection. You can edit
+ the values and save the settings in the new profile. You may
+ also want to rename the profile from <guilabel>New
+ Connection</guilabel> to something more appropriate. If you
+ click the <guibutton>Close</guibutton> button without saving
+ your changes using the <guibutton>Apply Changes</guibutton>
+ button, you will be prompted to save or discard your changes.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-file-close">
+
+ <title>Close</title>
+
+ <para>
+ Closes the &administrator; window and terminates the
+ connection to the MySQL server that had been established in
+ that window. If you have opened more than one instance
+ (program window, or process) of &administrator;, this command
+ will not close the other windows.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- File -->
+
+ <section id="mysql-administrator-menus-edit">
+
+ <title>Edit</title>
+
+ <para>
+ The <guimenu>Cut</guimenu>, <guimenu>Copy</guimenu>, and
+ <guimenu>Paste</guimenu> commands allow you to cut, copy, or
+ paste selected text in the
+ <link linkend="mysql-administrator-working-area">working
+ area</link>.
+ </para>
+
+ <section id="mysql-administrator-menus-edit-options">
+
+ <title>Options</title>
+
+ <para>
+ Opens the <link linkend="mysql-gui-options">Options
+ dialog</link> window.
+ </para>
+
+ </section>
+
+<!-- Options -->
+
+ </section>
+
+<!-- Edit -->
+
+ <section id="mysql-administrator-menus-view">
+
+ <title>View</title>
+
+ <remark>
+ Must be consistent options or sections?
+ </remark>
+
+ <para>
+ The <guimenu>View</guimenu> menu selects sections from the
+ <link linkend="mysql-administrator-sidebar">sidebar</link>.
+ Selecting an item from this menu is the same as clicking the
+ section with the same name from the sidebar.
+ </para>
+
+ </section>
+
+<!-- View -->
+
+ <section id="mysql-administrator-menus-tools">
+
+ <title>Tools</title>
+
+ <para>
+ The <guimenu>Tools</guimenu> menu starts other programs.
+ </para>
+
+ <section
+id="mysql-administrator-menus-tools-mysql-command-line-client">
+
+ <title>MySQL Command Line Client</title>
+
+ <para>
+ This menu item is available only if &administrator; finds the
+ executable file for the MySQL client. At the moment, it
+ searches locations such as <filename>C:\mysql\bin</filename>,
+ <filename>D:\mysql\bin</filename>, and
+ <filename>C:\<replaceable>program
+ directory</replaceable>\mysql\bin</filename> to find
+ <literal>mysql.exe</literal>. If the executable file is found,
+ you can start the command-line client with this command.
+ &administrator; will use the credentials provided in the
+ <link linkend="mysql-administrator-starting-connection">Connection
+ dialog</link> to start a server connection using the
+ command-line client.
+ </para>
+
+ </section>
+
+ <section
+id="mysql-administrator-menus-tools-windows-command-line">
+
+ <title>Windows Command Line</title>
+
+ <para>
+ Opens a DOS window.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- Tools -->
+
+ <section id="mysql-administrator-menus-help">
+
+ <title>Help</title>
+
+ <section id="mysql-administrator-menus-help-online-help">
+
+ <title>Help</title>
+
+ <para>
+ Opens a window displaying the &administrator; section of the
+ MySQL reference manual.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-help-report-bug">
+
+ <title>Report Bug to MySQL</title>
+
+ <para>
+ Opens a connection to the MySQL bug reporting system in your
+ web browser.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-help-mysql-website">
+
+ <title>Launch MySQL Website</title>
+
+ <para>
+ Opens a connection to the MySQL web site in your web browser.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-help-about">
+
+ <title>About ...</title>
+
+ <para>
+ Displays information about &administrator;.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- Help -->
+
+ </section>
+
+<!-- Menus -->
+
+</chapter>
Added: trunk/th/administrator/replication-status.xml
===================================================================
--- trunk/th/administrator/replication-status.xml (rev 0)
+++ trunk/th/administrator/replication-status.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 122, Lines Deleted: 0; 4200 bytes
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-replication-status">
+
+ <title>Replication Status</title>
+
+ <section id="mysql-administrator-replication-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The <guilabel>Replication Status</guilabel> sections give you a
+ visual overview of your MySQL replication master and slaves. The
+ server status icons beside each machine tells you which slave
+ machines are connected to the master and which ones are offline.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-replication-status-configure">
+
+ <title>Configuring Replication Servers</title>
+
+ <para>
+ To use the <guilabel>Replication Status</guilabel> section you
+ must be connected to the server that acts as the master in your
+ replication scheme. Your MySQL servers must be version 4 or higher
+ to use this feature.
+ </para>
+
+ <para>
+ For a slave server to show in the <literal>Replication
+ Status</literal> screen, it must register itself with the master
+ server. To have a slave server register itself with the master,
+ set the <literal>report-host</literal> option in your server
+ configuration (my.cnf/my.ini) file. See
+ <xref linkend="replication-options"/>.
+ </para>
+
+ <para>
+ You can also set the value in the <guilabel>Replication</guilabel>
+ tab of the <guilabel>Startup Variables</guilabel> section of
+ &administrator;.
+ </para>
+
+ </section>
+
+<!-- END CONFIGURATION -->
+
+ <section id="mysql-administrator-replication-status-using">
+
+ <title>Using the Replication Status Section</title>
+
+ <para>
+ Once your servers are configured, they will appear in the
+ <literal>Replication Status</literal> section, as seen in the
+ following figure:
+ </para>
+
+ <figure>
+ <title>The Replication Status section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/replication.png" lang="en" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">The Replication Status section</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ All servers are listed under the <guilabel>Hostname</guilabel>
+ column, along with their server ID, Port, and current status.
+ </para>
+
+ <para>
+ New servers that are not currently being monitored will have an
+ exclamation mark as their status symbol, and will be listed as a
+ <literal>New Instance</literal> in the <guilabel>Status</guilabel>
+ column of their entry.
+ </para>
+
+ <para>
+ Servers that are currently being monitored and are online will
+ have a green status icon and will be listed as
+ <literal>Available</literal> in the <guilabel>Status</guilabel>
+ column of their entry.
+ </para>
+
+ <para>
+ Servers that are currently not in contact with the master server
+ will have a red status icon and will be listed as <literal>Not
+ Available</literal>.
+ </para>
+
+ <para>
+ There will be a slight delay between a slave machine going offline
+ and having its status updated to allow for an adequate timeout in
+ the communications between master and slave.
+ </para>
+
+ <para>
+ To start monitoring a new server that is not currently being
+ monitored, click the <guibutton>Add Instance to Monitoring
+ List</guibutton> button. To stop monitoring a server that is
+ currently being monitored, click the <guibutton>Remove Instance
+ from monitoring List</guibutton> button.
+ </para>
+
+<!-- Replication Status -->
+
+ </section>
+
+<!-- END USING -->
+
+</chapter>
Added: trunk/th/administrator/restore.xml
===================================================================
--- trunk/th/administrator/restore.xml (rev 0)
+++ trunk/th/administrator/restore.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 166, Lines Deleted: 0; 5555 bytes
@@ -0,0 +1,166 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-restore">
+
+ <title>Restore</title>
+
+ <section id="mysql-administrator-restore-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The <guilabel>Restore</guilabel> section helps with disaster
+ recover by helping you restore backup files created using
+ &administrator;. See <xref linkend="mysql-administrator-backup" />
+ for more information on creating backups with &administrator;.
+ </para>
+
+ <para>
+ The backup files created by &administrator; are similar but not
+ identical to those created by <command>mysqldump</command>. A
+ consequence of the differences is that &administrator; cannot read
+ dump files created by <command>mysqldump</command>.
+ </para>
+
+ </section>
+
+<!-- END INTRODUCTION -->
+
+ <section id="mysql-administrator-restore-general">
+
+ <title>The General Tab</title>
+
+ <para>
+ In this tab, you specify which backup file should be restored, the
+ character set and format, and the target location for restored
+ tables.
+ </para>
+
+ <para>
+ To set any options on this tab, you must first open a backup file
+ by clicking the <guibutton>Open Backup File</guibutton> button at
+ the bottom of the window. When all options are set, you can click
+ the <guibutton>Start Restore</guibutton> button to begin the
+ restore process.
+ </para>
+
+ <para>
+ The following options are available:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>File to restore</guilabel>: Specify the path and
+ filename of the backup file. You can browse for that file by
+ clicking the <guibutton>Open Backup File</guibutton> button.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Target Schema</guilabel>: You can choose the
+ <guimenu>Original Schema</guimenu> option to have all tables
+ restored into their original databases. You can also choose
+ the <guimenu>New Schema ...</guimenu> option to restore all
+ tables into a new database. Finally you can choose from one of
+ the existing databases in the drop-down list to force all
+ tables to be restored to that database.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Backup Type</guilabel>: At the moment, the only
+ available option is <guimenu>SQL Files</guimenu>. Those are
+ backup files containing SQL statements such as those produced
+ by <literal>mysqldump</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Ignore Errors</guilabel>: Selecting this option
+ allows a user to continue with the restore operation even if
+ errors are encountered. However, results are not likely to be
+ 100% correct.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Create database(s) if they don't exist</guilabel>:
+ If a non-existent database is referenced it will automatically
+ be created if this option is checked.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>File Charset</guilabel>: Backup files created with
+ &administrator; are encoded in the <literal>utf8</literal>
+ character set. Backup files created with other tools such as
+ <literal>winmysqladmin</literal> may be encoded with other
+ character sets. Before a backup file can be successfully
+ imported you will need to specify its character set.
+ </para>
+
+ <para>
+ If you do not know the character set of your backup file,
+ click the <guibutton>Auto-Detect Character Set</guibutton>
+ button to have &administrator; attempt to determine it
+ automatically.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- END GENERAL -->
+
+ <section id="mysql-administrator-restore-restore-content">
+
+ <title>Restore Content</title>
+
+ <para>
+ If you do not wish to restore all the databases or tables listed
+ within your backup file, you can use the <guilabel>Restore
+ Content</guilabel> tab to limit which databases and tables are
+ restored.
+ </para>
+
+ <para>
+ After clicking the <guibutton>Analyze Backup File
+ Content</guibutton> button, a list of all databases and tables
+ contained within the backup file will be displayed.
+ </para>
+
+ <figure>
+ <title>The Restore Content tab</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/restore-content.png" lang="en" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">The Restore Content tab</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ To prevent a database or table from being restored, uncheck the
+ box next to the object's name.
+ </para>
+
+ </section>
+
+<!-- Restore Content -->
+
+</chapter>
Added: trunk/th/administrator/server-connections.xml
===================================================================
--- trunk/th/administrator/server-connections.xml (rev 0)
+++ trunk/th/administrator/server-connections.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 146, Lines Deleted: 0; 5587 bytes
@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-server-connections">
+
+ <title>Server Connections</title>
+
+ <section id="mysql-administrator-server-connections-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ This section allows you to view and manage the current connections
+ to the server (also called threads). If you have the
+ <literal>PROCESS</literal> privilege, you can see all threads. If
+ you have the <literal>SUPER</literal> privilege, you can also
+ terminate threads other than your own. (Note that the
+ <literal>SUPER</literal> privilege is available for MySQL servers
+ as of version 4.0.3 only.) Otherwise, you can see your own threads
+ only. See <xref linkend="show-processlist"/>, for more
+ information. See <xref linkend="privileges-provided"/>, for more
+ information on the <literal>PROCESS</literal> and the
+ <literal>SUPER</literal> privilege (and other available privileges
+ as well).
+ </para>
+
+ <note>
+ <para>
+ When you click the
+ <link linkend="mysql-administrator-server-connections-threads">Server
+ Connections</link> section You will see an additional thread for
+ the user you logged in as because the values displayed are
+ retrieved from the MySQL server via an additional separate
+ connection.
+ </para>
+ </note>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-server-connections-threads">
+
+ <title>Threads</title>
+
+ <para>
+ This tab allows you to view all connections to the server
+ (threads). By default, threads are sorted by their
+ <literal>PID</literal> (MySQL process identification number), but
+ you can change that order by clicking on the appropriate headings
+ (<guilabel>User</guilabel>, <guilabel>Host</guilabel>, etc.).
+
+ <remark>
+ [SH] This is not implemented yet.
+ </remark>
+
+ You can select one or more threads using the mouse or the
+ keyboard.
+ </para>
+
+ <para>
+ To reload the process list from the server, press the
+ <guibutton>Refresh</guibutton> button.
+ </para>
+
+ <para>
+ If you have selected one or more threads, you can terminate them
+ by clicking the <guibutton>Kill Thread</guibutton> button, or by
+ right-clicking on that thread. Remember that you need the
+ <literal>PROCESS</literal> privilege to see threads other than
+ your own, and the <literal>SUPER</literal> privilege to kill
+ threads other than your own. Furthermore, note that
+ &administrator; imposes a restriction that prevents you from
+ terminating your own threads. On Windows, using the
+ <guibutton>Kill Thread</guibutton> button on your own threads has
+ no effect; on Linux, that button is disabled when selecting your
+ own threads.
+ </para>
+
+ </section>
+
+<!-- Threads -->
+
+ <section id="mysql-administrator-server-connections-user-connections">
+
+ <title>User Connections</title>
+
+ <para>
+ This tab displays all connections to the server (threads), but in
+ a different way than the
+ <link
+ linkend="mysql-administrator-server-connections-threads">Threads</link>
+ tab does: You will see users rather than individual threads. The
+ number of connections for each user is listed under
+ <guilabel>Num.</guilabel>. Right-clicking on a username and
+ selecting <guimenu>Show User Infos</guimenu> displays the
+ <guilabel>Full Name</guilabel> and the
+ <guilabel>Description</guilabel>, as specified in the
+ <guilabel>User Information</guilabel> tab of the
+ <link
+ linkend="mysql-administrator-user-administration-user-information"
+ >User
+ Administration</link> section. Initially, users are sorted by
+ their MySQL <literal>Username</literal>, but you can change the
+ order by clicking on the headings (<guilabel>Num.</guilabel>,
+ <guilabel>Full Name</guilabel>, or
+ <guilabel>Description</guilabel>).
+
+ <remark>
+ [SH] Not implemented yet.
+ </remark>
+
+ Clicking on a username will display the individual threads of that
+ user in the lower box of the tab, ordered by
+ <guilabel>PID</guilabel>. Likewise, you can change the order by
+ clicking on one of the headings.
+
+ <remark>
+ [SH] Not implemented yet.
+ </remark>
+ </para>
+
+ <para>
+ Clicking on a user will enable the <guibutton>Kill
+ User</guibutton> button, allowing you to terminate all threads of
+ that user with a single click. This command is also available by
+ right clicking on the username. Clicking on an individual thread
+ in the lower box enables the <guibutton>Kill Thread</guibutton>
+ button, which is used to terminate a connection. This command is
+ also available by right clicking on a thread.
+ </para>
+
+ <para>
+ To reload the user list from the server, press the
+ <guibutton>Refresh</guibutton> button.
+ </para>
+
+ </section>
+
+<!-- User Connections -->
+
+</chapter>
Added: trunk/th/administrator/server-information.xml
===================================================================
--- trunk/th/administrator/server-information.xml (rev 0)
+++ trunk/th/administrator/server-information.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 158, Lines Deleted: 0; 4283 bytes
@@ -0,0 +1,158 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-server-information">
+
+ <title>Server Information</title>
+
+ <para>
+ Provides basic information about connection, server, and client.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Connected to MySQL Server Instance
+
+ <remark>
+ [SH] Mike: The label name is gruesome (why not just
+ "Connection"?).
+ </remark>
+ </para>
+
+ <para>
+ Information about the parameters used to connect to the MySQL
+ server.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Username:</guilabel> Username used for the current
+ connection to the MySQL server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Hostname:</guilabel> The name of the machine
+ hosting the MySQL server. This is either identical to the
+ name listed in <guilabel>Network Name</guilabel>, or it is
+ <literal>localhost</literal>. The former indicates that you
+ are connecting to a server that either runs on a remote
+ machine, or that you have specified a hostname different
+ from <literal>localhost</literal> when connecting. The
+ latter indicates that the MySQL server runs on the same
+ machine where MySQL Administrator runs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Port</guilabel>: The port used for connecting to
+ the MySQL server.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ Server Information
+ </para>
+
+ <para>
+ Information about the MySQL server and its host.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>MySQL Version</guilabel>: The version of the MySQL
+ server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Network Name</guilabel>: The name of the machine
+ hosting the MySQL server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <remark>
+ [PD] "IP" is ambiguous because there are IP numbers and IP
+ addresses.
+ </remark>
+
+ <guilabel>IP</guilabel>: The IP number of the MySQL server
+ host.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ Client Information
+ </para>
+
+ <para>
+ Information about &administrator; and the host client.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Version</guilabel>: The version of
+ &administrator;, and the version number of the MySQL
+ client/server protocol.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Network name</guilabel>: The name of the host
+ where MySQL Administrator runs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>IP</guilabel>: The IP number of the MySQL
+ Administrator host.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Operating System</guilabel>: Information about the
+ operating system on which &administrator; runs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Hardware</guilabel>: Information about the
+ hardware on which &administrator; runs.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ </itemizedlist>
+
+</chapter>
Added: trunk/th/administrator/server-logs.xml
===================================================================
--- trunk/th/administrator/server-logs.xml (rev 0)
+++ trunk/th/administrator/server-logs.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 184, Lines Deleted: 0; 6574 bytes
@@ -0,0 +1,184 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-server-logs">
+
+ <title>Server Logs</title>
+
+ <section id="mysql-administrator-server-logs-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The <literal>Server Logs</literal> section provides easy access to
+ the various log files generated by the MySQL server. You can
+ access the server's error log, slow query log, and general log
+ using this section.
+ </para>
+
+ <para>
+ This section has one tab for each of the log files, and each tab
+ is split into two boxes. Above the boxes, there is a bar which
+ allows you to navigate through larger log files by breaking the
+ log file into individual pages. Clicking in the bar will display
+ the individual pages. The light blue area represents the portion
+ of the log file you are currently viewing.
+ </para>
+
+ <figure>
+ <title>Displaying entries from the middle of the General Log</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/server-logs-general-log.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Displaying entries from the middle of the
+ General Log</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ You can only view log files that are stored on the machine where
+ &administrator; is running, you cannot view log files on a remote
+ machine.
+ </para>
+
+ <para>
+ Also note that some tabs may be disabled. If a tab is disabled it
+ indicates that the log file in question has not been enabled on
+ the MySQL server. You can enable the various log files in the
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link> section.
+ </para>
+
+ <remark>
+ Below refers to new image not shown above
+ </remark>
+
+ <para>
+ The left box (labeled <guilabel>Events of page
+ <replaceable>x</replaceable> /
+ <replaceable>y</replaceable></guilabel>) displays the major events
+ that have occurred on the current page of the log file. The right
+ box (labeled <guilabel>Page Content</guilabel>) displays the
+ detailed lines of the log file. By clicking on an event in the
+ left box, the first detailed entry of the event will be
+ highlighted in the right box.
+ </para>
+
+ <para>
+ In addition to the log file tabs, the <literal>Server
+ Logs</literal> section has four action buttons for managing log
+ information:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guibutton>Open Other File</guibutton> will allow you to open
+ a log file other than the currently active log file. This can
+ be useful in situations where you rotate your log files as it
+ allows you to open log files that have been rotated out of
+ active use.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guibutton>Search</guibutton> opens a dialog where you can
+ specify a search term to look for in the log file. If it's
+ found, it will be marked as selected in the right box. This
+ command is also available by right clicking in the right box
+ and choosing the <guimenu>Search ...</guimenu> option.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guibutton>Save Log Page</guibutton> opens a dialog that
+ allows you to specify the path and file name where the current
+ page of the log file should be stored. By default,
+ &administrator; suggests <literal>ErrorLog.txt</literal>,
+ <literal>SlowLog.txt</literal>, or
+ <literal>GeneralLog.txt</literal> as a filename. Note that
+ executing this command does not affect the actual log file in
+ any way; it just creates a copy of the
+ <emphasis>current</emphasis> log file contents that you may
+ store for documenting or analyzing. This command is also
+ available by right clicking in the right box and choosing the
+ <guimenu>Save log Page ...</guimenu> option.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guibutton>Refresh</guibutton> will reload the log files.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-server-logs-error-log">
+
+ <title>Error Log</title>
+
+ <para>
+ Displays the MySQL server's error log. The error log file contains
+ information indicating when the MySQL server was started and
+ stopped and also any critical errors found when running. See
+ <xref linkend="error-log"/>, for more information about that log
+ file.
+ </para>
+
+ </section>
+
+<!-- Error Log -->
+
+ <section id="mysql-administrator-server-logs-slow-log">
+
+ <title>Slow Log</title>
+
+ <para>
+ Displays the MySQL server's slow query log. If enabled (which you
+ can do in the
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link> section), the MySQL server writes a log file
+ containing all SQL commands that took more than a specific number
+ of seconds to execute. (That number can be configured by the
+ <literal>long-query-time</literal> variable; its default value is
+ 10 seconds.) The time it takes to get the initial table locks is
+ not counted as execution time. For more information about this log
+ file, see <xref linkend="slow-query-log"/>.
+ </para>
+
+ </section>
+
+<!-- Slow Log -->
+
+ <section id="mysql-administrator-server-logs-general-log">
+
+ <title>General Log</title>
+
+ <para>
+ Displays the MySQL server's general query log. This log can be
+ very useful when you suspect an error in a client and want to know
+ exactly what the MySQL server thought the client sent to it. For
+ more information about that log file, see
+ <xref linkend="query-log"/>.
+ </para>
+
+ </section>
+
+<!-- General Log -->
+
+</chapter>
Added: trunk/th/administrator/service-control.xml
===================================================================
--- trunk/th/administrator/service-control.xml (rev 0)
+++ trunk/th/administrator/service-control.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 330, Lines Deleted: 0; 11495 bytes
@@ -0,0 +1,330 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-service-control">
+
+ <title>Service Control</title>
+
+ <section id="mysql-administrator-service-control-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ This section shows how to start and stop the MySQL server you are
+ connected to. Currently, this is only possible if the server is
+ running on the same machine that hosts &administrator;.
+
+ <remark>
+ [PL] and if that service has been configured.
+ </remark>
+
+ You cannot start and stop MySQL servers on remote machines.
+
+ <remark>
+ [PL]If the server runs as a stand-alone application, the Service
+ Control section will not be enabled. (what do these remarks
+ mean?
+ </remark>
+ </para>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-service-control-start-stop-service">
+
+ <title>Start/Stop Service</title>
+
+ <para>
+ The <guilabel>Start/Stop Service</guilabel> tab displays the
+ status of the MySQL service. This service starts and stops the
+ MySQL server. Under <guilabel>Service Status</guilabel>, a text
+ message indicates whether or not the service has been started. If
+ the service is running, the button label is <guibutton>Stop
+ Service</guibutton>. Click it to stop the server. If the service
+ is stopped, the button label is <guibutton>Start
+ Service</guibutton>. Click it to start the service.
+ </para>
+
+ <para>
+ Under <guilabel>Log Messages</guilabel>, you will find messages
+ that the MySQL server produces when it starts or stops. Messages
+ produced by the server during startup look something like this:
+ </para>
+
+<programlisting>
+Trying to start the server ...
+040119 18:33:41 InnoDB: Started
+MySql: ready for connections.
+Version: '4.0.16-max-nt-log' socket: '' port: 3306
+Server was started.
+</programlisting>
+
+ <para>
+ When the server stops, it produces messages such as these:
+ </para>
+
+<programlisting>
+Trying to stop the server ...
+040119 18:31:45 MySql: Normal shutdown
+040119 18:31:46 MySql: Forcing close of thread 11 user:
+'superuser'
+040119 18:31:46 MySql: Forcing close of thread 8 user: 'superuser'
+...
+Server was stopped.
+</programlisting>
+
+ <para>
+ The details and format of the messages might vary depending on the
+ version of the MySQL server you are using and its configuration.
+ </para>
+
+ </section>
+
+<!-- Start/Stop Service -->
+
+ <section id="mysql-administrator-service-control-configure-service">
+
+ <title>Configure Service</title>
+
+ <para>
+ Use this tab to configure the Windows service that starts and
+ stops the MySQL server and to set server options. This tab is
+ specific to MySQL servers running under operating systems of the
+ Windows NT family, including Windows 2000, and Windows XP; it is
+ not available for servers running under a different operating
+ system. Obviously, you need to have a Windows service installed
+ before you can configure it. See
+ <xref linkend="windows-start-service"/>, for more information on
+ how to set up a Windows service.
+ </para>
+
+ <para>
+ Note that if you have more than one MySQL server running as a
+ Windows service, you should run &administrator; in
+ <link
+linkend="mysql-administrator-starting-configure-service">configure-service
+ mode</link> to administer these services. In normal mode, you can
+ only administer the Windows service listed first in the Windows
+ service manager, no matter which server you are connected to.
+
+ <remark>
+ Add link
+ </remark>
+ </para>
+
+ <para>
+ Note that the settings in the <guilabel>Server Features</guilabel>
+ group take effect only after restarting the MySQL server.
+ </para>
+
+ <para>
+ The following settings are available:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Service Settings
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Launch MySQL server automatically</guilabel>: If
+ checked, the Windows service starts the MySQL server
+ automatically on operating system startup.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Display Name</guilabel>: The display name of the
+ Windows service (not the service name!) as it will appear
+ in the Windows services manager when displaying the
+ properties of that service.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Service Description</guilabel>: The description
+ of the Windows service as it will appear in the Windows
+ services manager.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ Option File
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Config Filename</guilabel>:
+
+ <remark>
+ [SH] Mike: "Config" is ugly. Suggestion: Filename
+ </remark>
+
+
+
+ <remark>
+ [PD] Right. Don't use truncated words like Config in
+ labels. Should either be written out, or, if that's too
+ long, try to pick a different term.
+ </remark>
+
+ You can enter the pathname of the server option file.
+ MySQL will enter that information in the Windows registry,
+ and the Windows service starting the MySQL server will use
+ that file, rather than the default file
+ (<filename>C:\<replaceable>windows installation
+ directory</replaceable>\my.ini</filename>). <emphasis>Note
+ that this is available for MySQL servers as of version
+ 4.0.3 only.</emphasis> See
+ <xref linkend="windows-create-option-file"/>, for details
+ about the server option files.
+
+ <remark>
+ [PD] If this file is passed to the server as the
+ --defaults-option (which I suspect is the case), the
+ server will read only the [mysqld] option group in the
+ file.
+ </remark>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Section Name</guilabel>:
+
+ <remark>
+ [SH] FILL IN
+ </remark>
+
+ Setting a value other than <literal>mysqld</literal> is
+ most useful when running multiple servers; see
+ <xref linkend="multiple-windows-servers"/>.
+
+ <remark>
+ [SH] This is likely to change; need to document the
+ changed behaviour.
+ </remark>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ Server Features
+ </para>
+
+ <para>
+ <emphasis>Note that all server features will only take effect
+ after the MySQL server has been restarted.</emphasis>
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Support for InnoDB</guilabel>: If checked, the
+ MySQL server is started with support for InnoDB tables. If
+ unchecked, it doesn't start the InnoDB storage engine;
+ this saves memory, but InnoDB tables cannot be used. If
+ this checkbox is unchecked and grayed out, it means that
+ your MySQL server isn't compiled with support for InnoDB
+ tables. (This is, for example, true for some versions that
+ run under a commercial license.) For more information on
+ InnoDB tables, see <xref linkend="storage-engines"/>.
+ </para>
+
+ <para>
+ <emphasis>Be careful when disabling this option! If any
+ databases on the MySQL server contain InnoDB tables,
+ disabling this option makes those tables
+ inaccessible.</emphasis>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Support for BDB</guilabel>: If checked, the
+ MySQL server is started with support for BDB tables. If
+ unchecked, it doesn't start the BDB storage engine; this
+ saves memory, but BDB tables cannot be used. If this
+ checkbox is unchecked and grayed out, it means that your
+ MySQL server isn't compiled with support for BDB tables.
+ (This is, for example, true for non-max versions.) For
+ more information on BDB tables, see
+ <xref linkend="storage-engines"/>.
+ </para>
+
+ <para>
+ <emphasis>Be careful when disabling this option! If any
+ databases on the MySQL server contain BDB tables,
+ disabling this option makes those tables
+ inaccessible.</emphasis>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Named Pipes</guilabel>: On operating systems of
+ the Windows NT family, including Windows 2000, and Windows
+ XP, you may use named pipes to connect to a MySQL server
+ running on the local machine, rather than connecting via
+ TCP/IP. If this option is checked, named pipe connections
+ are allowed. Note that named pipes are slower than TCP/IP
+ in many Windows configurations. See
+ <xref linkend="windows-select-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Debug Information (slow)</guilabel>: If checked,
+ the MySQL server is started with an option that allows for
+ easier debugging of problems. Using this option slows down
+ the server significantly, so it is recommended only for
+ debugging purposes. If the MySQL server has not been
+ compiled with debugging support, this option is grayed
+ out. See <xref linkend="server-options"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Path to Binary</guilabel>: Contains the pathname
+ of the MySQL server binary file as it is listed in the
+ Windows service manager (for example
+ <literal>C:\mysql\bin\mysqld-max-nt</literal>). Note that
+ the the Windows service manager does not display the
+ <literal>.exe</literal> extension.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- Configure Service -->
+
+</chapter>
Added: trunk/th/administrator/startup-variables.xml
===================================================================
--- trunk/th/administrator/startup-variables.xml (rev 0)
+++ trunk/th/administrator/startup-variables.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 359, Lines Deleted: 0; 14457 bytes
@@ -0,0 +1,359 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-startup-variables">
+
+ <title>Startup Variables</title>
+
+ <section id="mysql-administrator-startup-variables-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ This section allows you to set variables that the MySQL server
+ reads on startup. These variables are stored in the option file of
+ the server. On Windows, the option file is called
+ <filename>my.ini</filename>, and it is located in the Windows
+ installation directory (for example,
+ <filename>C:\WinNT\my.ini</filename>). Note that it can
+ alternatively be stored in <filename>C:\</filename>, in which case
+ it is named <filename>my.cnf</filename>. Also note that there can
+ be more than one option file. On operating systems other than
+ Windows, the option file is called <filename>my.cnf</filename>,
+ regardless of where it resides. On Windows, &administrator; allows
+ you to store the option file in any location you specify. See
+ <xref linkend="option-files"/> for more information.
+ </para>
+
+ <para>
+ <emphasis>Note that the server reads variables stored in the
+ option files only at server startup. After changing an option
+ file, you must restart the server for the changes to take effect.
+ You can do this using the <guibutton>Stop Server</guibutton> and
+ <guibutton>Start Server</guibutton> buttons in the
+ <link
+linkend="mysql-administrator-service-control-start-stop-service">Service
+ Control</link> section.</emphasis>
+ </para>
+
+<!--
+
+ <para>
+ The <literal>Startup Variables</literal> section has three tabs:
+ one for general variables, one for variables specific for the
+ MyISAM storage engine, and one for variables specific for the
+ InnoDB storage engine.
+ </para>
+
+ <para>
+ Each tab has two buttons labeled <guibutton>Apply
+ changes</guibutton> and <guibutton>Discard changes</guibutton>.
+
+ <remark>
+ [SH] Mike: Capitalise "changes"?
+ </remark>
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ If you click <guibutton>Apply changes</guibutton>, the
+ variables and their values will be written to the option
+ file. If a parameter exists in that file, it will be
+ assigned a new value; if it does not exist, a new line is
+ added to the option file with this parameter. Above that
+ line, and additional comment is written giving a short
+ explanation for that parameter.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Clicking <guibutton>Discard</guibutton> discards any changes
+ made in the fields of the tab, and resets them to their
+ previous values. You will be prompted to confirm that you
+ really want to discard the changes. If you click
+ <guibutton>Yes</guibutton>, nothing will be changed in the
+ option file (<literal>my.ini</literal> or
+ <literal>my.cnf</literal>).
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Some fields include a drop-down box where you can either select
+ <guimenu>K</guimenu> to indicate that the value is specified in
+ kilobytes, or <guimenu>M</guimenu> to indicate that it is in
+ megabytes.
+ </para>
+
+ -->
+
+ </section>
+
+<!--
+ <section id="mysql-administrator-startup-variables-general-variables">
+ <title>General Variables</title>
+ <para>
+ This tab allows you to configure variables that affect the networking
+behavior, memory usage and directory locations of the MySQL server.
+Note that changes will only be written to the option files when you
+click the <guibutton>Apply Changes</guibutton> button. They take
+effect only after restarting the server.
+ <itemizedlist>
+ <listitem><para>
+ Networking
+ <itemizedlist>
+ <listitem><para>
+ <literal>Use socket/named pipe file</literal>: If checked,
+connections to the MySQL server from clients on the local host will not
+use the
+TCP/IP protocol. Instead, they use a Unix socket file (on Unix-like
+systems) or a named pipe (on Windows NT family systems such as Windows
+NT, Windows 2000, and Windows XP). This can make client-server
+communication significantly faster on some systems, but it will be
+slower in many Windows configurations (see <xref linkend="windows-select-server"/>).
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem>
+ <para>
+ Memory Usage <remark>[SH] Mike: usage => Usage</remark>
+ </para>
+ <para>
+ See <xref linkend="show-variables"/> for more information on the variables that influence that
+memory usage.
+ <itemizedlist>
+ <listitem><para>
+ <literal>Max allowed packet</literal>: The maximum size of one
+packet sent from the client to the server, or the other way around. Note
+that this can be set to a maximum value of 16 kilobytes (k) for MySQL
+version 3.23<remark>[UB] I think we should not care about 3.*
+servers.</remark>, and to 1 gigabyte (1024 M) as of MySQL version 4.0.
+ </para></listitem>
+ <listitem><para>
+ <literal>Table cache</literal>: The number of tables that the
+MySQL server can keep open simultaneously. See <xref linkend="table-cache"/>, for more
+information on this parameter.
+ </para></listitem>
+ <listitem><para>
+ <literal>Record buffer</literal>: <remark>[SH] Mike:
+record-buffer is the old name, which might be confusing to use
+here. read-buffer-size, so better call it "Read buffer".</remark>
+The size of this parameter influences performance when the MySQL
+server performs many sequential table scans.
+ </para></listitem>
+ <listitem><para>
+ <literal>Sort buffer</literal>: The size of this buffer
+influences the performance of sort operations, such as in <literal>ORDER
+BY</literal> or <literal>GROUP BY</literal> clauses.
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem>
+ <para>
+ Directories <remark>[SH] Mike: I wonder what happens if you change
+Base or Data directory without moving the files. Are these things
+that we actually want people to be able to set in MySQL
+Administrator?</remark>
+<remark>
+[PD] Perhaps a warning is in order, to the effect that the user must
+make sure the directories really are located where specified here?
+[UB] Sounds reasonable.
+</remark>
+ </para>
+ <para>
+ See <xref linkend="installation-layouts"/>, for more information about the MySQL directories.
+ <itemizedlist>
+ <listitem><para>
+ <literal>Base directory</literal>: The MySQL installation
+directory.
+ </para></listitem>
+ <listitem><para>
+ <literal>Data directory</literal>: The location where MySQL
+stores databases and tables. Note that there may be other locations
+where some databases and tables get stored; this may be the case for
+InnoDB tables if the InnoDB tablespace is located somewhere other than
+in the data directory.
+ </para></listitem>
+ <listitem><para>
+<remark>
+[PD] "Temp" is a truncated word.
+</remark>
+ <literal>Temp directory</literal>: The location MySQL uses to
+store temporary files.
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ </itemizedlist>
+ </para>
+ </section>
+ <section id="mysql-administrator-startup-variables-myisam-variables">
+ <title>MyISAM Variables</title>
+ <para>
+ This tab allows you to set buffers that the server uses for the
+MyISAM storage engine, and that affect memory usage. For more
+information about the key buffer (variable name:
+<literal>key-buffer-size</literal>) and the sort buffer (variable
+name: <literal>sort-buffer-size</literal>), see <xref linkend="show-variables"/>.
+See <xref linkend="myisam"/>, for more
+information about the MyISAM storage engine.
+ </para>
+ </section>
+ <section id="mysql-administrator-startup-variables-innodb-variables">
+ <title>InnoDB Variables</title>
+ <para>
+ This tab allows you to set various options for the InnoDB storage
+engine. For more information about the InnoDB storage engine, see <xref linkend="innodb"/>.
+ </para>
+ <itemizedlist>
+ <listitem><para>
+ <literal>Deactivate InnoDB</literal>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>Deactivate InnoDB</literal>: If checked, the InnoDB
+storage engine will be disabled. This will reduce memory usage if
+you do not want to use InnoDB tables. You can accomplish the same
+effect by unchecking the <literal>Support for InnoDB</literal>
+checkbox in the <link
+linkend="mysql-administrator-service-control-configure-service"><
+literal>Configure Service</literal> tab of the <literal>Service
+Control</literal> section</link>. There is a slight difference,
+though: Checking this option will disable the InnoDB engine by
+writing <literal>skip-innodb</literal> to the option file, while
+unchecking the <literal>Support for InnoDB</literal> checkbox
+will select a server binary that does not support the InnoDB
+engine.
+ </para>
+ <para>
+ <emphasis>Be careful when enabling that option! If there are
+databases on the MySQL server that contain InnoDB tables, then
+those tables will be unaccessible after enabling that
+option.</emphasis>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>
+ <literal>Memory</literal>
+ <itemizedlist>
+ <listitem><para>
+ <literal>Buffer Pool Size</literal>: Sets the value of the
+<literal>innodb-buffer-pool-size</literal> variable. Setting this
+value high reduces the need for disk access, which makes data
+access in tables faster. Setting it too high may, however, cause
+paging (which means disk accesses) in the operating system. See <xref linkend="innodb-start"/>.
+ </para></listitem>
+ <listitem><para>
+ <literal>Add. mem Pool Size</literal>: <remark>[SH] Mike: Add.
+Mem. Pool Size?</remark> This is the memory allocated by InnoDB to
+store internal data, like data dictionary information. A sensible
+value of this option depends on the number of InnoDB tables you
+are using. See <xref linkend="innodb-start"/>.
+ </para></listitem>
+ <listitem><para>
+ <literal>Use AWE Memory</literal>: <remark>[SH] Mike: memory =>
+Memory</remark> If checked, InnoDB stores the buffer pool in the
+AWE (Address Windowing Extension) memory. AWE memory is available
+in Windows operating systems only. The prerequisites of using this
+option are that the machine where the MySQL server runs on has
+more than 4 GB of memory, and that the Windows version it runs on
+supports AWE memory. <remark>[SH] Mike: Will the "AWE" options
+appear in the Gnome/Mac OS versions?</remark> <remark>[SH] I found
+no explanation what the usage of AWE memory is good for. It's
+probably faster, but I can only guess so far. Also, the manual
+says that 500M is a good value, but doesn't say why. I asked
+Heikki.</remark> For more information about AWE memory, see
+<xref linkend="innodb-start"/>.
+ </para></listitem>
+ <listitem><para>
+ <literal>AWE mem Pool Size</literal>: <remark>[SH] Mike: mem =>
+Mem.?</remark>
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>
+ <literal>Datafiles</literal>
+ <itemizedlist>
+ <listitem><para>
+ <literal>Data File Paths</literal>: <remark>[SH] Mike: Data File
+=> Datafile</remark> <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ Adding and removing datafiles: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ Extending last datafile: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Data directory</literal>: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>
+ <literal>Logfiles</literal> <remark>[SH] Mike: Log Group Dir and Log
+Archive Dir fields should be next to each other, I believe.</remark>
+ <itemizedlist>
+ <listitem><para>
+ <literal>Log Group Dir</literal>: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Log Files in Group</literal>: <remark>[SH] FILL
+IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Mirrored Log Groups</literal>: <remark>[SH] FILL
+IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Log File Size</literal>: <remark>[SH] Mike: Log File =>
+Logfile</remark> <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Log Buffer Size</literal>: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Flush Log at</literal>: <remark>[SH] Mike: I'd remove
+"at"</remark> <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Flush Method</literal>: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Log archive</literal>: <remark>[SH] Mike: archive =>
+Archive</remark> <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Log Archive Dir</literal>: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>
+ <literal>Various</literal><remark>[SH] Mike: Various =>
+Miscellaneous?</remark>
+ <itemizedlist>
+ <listitem><para>
+ <literal>Lock Wait Timeout</literal>: <remark>[SH] FILL
+IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>Open Files</literal>: <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ <listitem><para>
+ <literal>File IO Threads</literal>: <remark>[SH] Mike: IO =>
+I/O?</remark> <remark>[SH] FILL IN</remark>
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ </itemizedlist>
+ </section>
+ -->
+
+</chapter>
Added: trunk/th/administrator/tray-monitor.xml
===================================================================
--- trunk/th/administrator/tray-monitor.xml (rev 0)
+++ trunk/th/administrator/tray-monitor.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 120, Lines Deleted: 0; 4286 bytes
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<appendix id="mysql-administrator-appendix-tray-monitor">
+
+ <title>The &tray_monitor;</title>
+
+ <para>
+ The &tray_monitor; is a tool that allows you to monitor the status
+ of your local mysql server through an indicator that resides in the
+ system tray. The &tray_monitor; also gives quick access to the
+ various MySQL GUI tools through its context menu.
+ </para>
+
+ <para>
+ To start the &tray_monitor;, you can either execute the
+ <filename>MySQLSystemTrayMonitor.exe</filename> application that
+ resides in your &administrator; installation directory, or choose
+ the <guimenu>MySQL System Tray Monitor</guimenu> option of the
+ <guimenu>Tools</guimenu> menu.
+ </para>
+
+ <para>
+ Once the &tray_monitor; is running, it resides in the system tray
+ and provides visual status information for your MySQL server. A
+ green icon is displayed at the top left corner of the &tray_monitor;
+ if the MySQL server is running, and a red icon is displayed if the
+ service is stopped. In addition, the CPU load may optionally be
+ displayed along the right side of the &tray_monitor;.
+ </para>
+
+ <figure>
+ <title>The &tray_monitor;</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/system-tray.png" lang="en" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">The &tray_monitor;</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ If you right-click on the &tray_monitor;, a pop-up menu will appear,
+ listing all installed MySQL services and their individual statuses.
+ For each service, the following options are available:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guimenu>Shutdown Instance:</guimenu> this will begin the
+ shutdown operation on the selected running service.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Start Instance:</guimenu> this will start a currently
+ stopped server instance.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Configure Instance:</guimenu> this will launch the
+ &administrator; in configure service mode for the currently
+ selected instance. See
+ <link linkend="mysql-administrator-starting-configure-service">Configure
+ Service Mode</link> for more details.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Monitoring Options:</guimenu> currently the
+ <guimenu>Monitoring Options</guimenu> submenu has one available
+ option: <guimenu>Ignore Instance State</guimenu>.
+ <guimenu>Ignore Instance State</guimenu> will cause the
+ &tray_monitor; to stop monitoring the selected service.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ In addition to the service controls, you can also start the
+ &query_browser; and &administrator; from the pop-up menu.
+ </para>
+
+ <para>
+ The <guimenu>Manage MySQL Instances</guimenu> option of the
+ <guimenu>Actions</guimenu> menu can be used to start &administrator;
+ in configure service mode so you can manage your server
+ configurations. See
+ <link linkend="mysql-administrator-starting-configure-service">Configure
+ Service Mode</link> for more details.
+ </para>
+
+ <para>
+ The <guimenu>Monitor Options</guimenu> menu has two options, which
+ affect the general behavior of the &tray_monitor;. <guimenu>Display
+ CPU Load</guimenu> determines whether the CPU usage is displayed on
+ the right of the &tray_monitor;. <guimenu>Launch Monitor after Login
+ </guimenu>
+
+ <remark>
+ [MH] APPLICATION CAPITALIZATION ERROR
+ </remark>
+
+ sets the &tray_monitor; to launch when you log into Windows.
+ </para>
+
+</appendix>
Added: trunk/th/administrator/user-administration.xml
===================================================================
--- trunk/th/administrator/user-administration.xml (rev 0)
+++ trunk/th/administrator/user-administration.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 603, Lines Deleted: 0; 21650 bytes
@@ -0,0 +1,603 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<chapter id="mysql-administrator-user-administration">
+
+ <title>User Administration</title>
+
+ <section id="mysql-administrator-user-administration-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ This section shows how to administer existing users, add new
+ users, and delete existing users. For more information on the
+ MySQL user account management and privilege system, see
+ <xref linkend="user-account-management"/>.
+ </para>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-user-administration-user-accounts">
+
+ <title>User Accounts</title>
+
+ <para>
+ Existing users are listed in the lower left area of the
+ <link linkend="mysql-administrator-sidebar">sidebar</link>. If
+ there are many user accounts on your MySQL server, the field with
+ the magnifying glass icon may be handy for filtering the users you
+ are looking for. Typing in <literal>t</literal> or
+ <literal>T</literal>, for example, will set the filter to users
+ whose names begin with a <literal>t</literal>. The filter works in
+ a case-insensitive fashion.
+ </para>
+
+ <para>
+ If you are an experienced MySQL user, you will notice that users
+ are not listed in the typical MySQL way
+ (<literal><replaceable>user</replaceable>@<replaceable>host
+ </replaceable></literal>), but rather with their usernames only.
+ If double clicking on a username does not show subcategories for
+ that user, this means that the user's privileges are not
+ restricted to a specific host, or hosts. If there are
+ subcategories, the user's privileges are restricted to a specific
+ host, or set of hosts. You may assign various (and different) sets
+ of privileges, depending on the host from which the user connects
+ to the MySQL server. That concept is described in detail in
+ <xref linkend="connection-access"/>.
+ </para>
+
+ <para>
+ <emphasis>Note that &administrator; has a different concept of
+ what a <literal>user</literal> is than MySQL has. In MySQL, a user
+ is always identified by a
+ <literal>username</literal>/<literal>host</literal> combination.
+ This means that, for example, <literal>'brian'@'%'</literal> may
+ be a user completely different from
+ <literal>'brian'@'localhost'</literal>. The former might be
+ <literal>Brian Miller</literal>, while the latter might be
+ <literal>Brian Schultz</literal>. That distinction does not hold
+ true for &administrator;: User <literal>brian</literal> is always
+ a particular user, no matter from which host he connects to the
+ MySQL server. That said, <literal>'brian'@'%'</literal> may still
+ have privileges different from
+ <literal>'brian'@'localhost'</literal>.</emphasis>
+ </para>
+
+ <figure>
+ <title>User accounts</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/user-accounts.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">User accounts</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ For example, you might have a user called
+ <literal>superuser</literal>. If double clicking on that username
+ shows two subcategories, <literal>localhost</literal> and
+ <literal>athena</literal>, this means that the user has a specific
+ set of privileges if he/she connects from
+ <literal>localhost</literal>, and a (probably different) set of
+ privileges if he/she connects from <literal>athena</literal>.
+ </para>
+
+ <para>
+ Right clicking on a username, or on one of the subcategories a
+ user might have, provides access to the following commands:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guimenu>Add a new User</guimenu>: Selecting this command adds
+ a new user with the default name <literal>New User</literal>
+ to the user list. You will have to fill in at least a username
+ in the <guilabel>MySQL User</guilabel> field of the
+ <link
+linkend="mysql-administrator-user-administration-user-information">User
+ Information</link> tab, which, after applying this change,
+ will also rename that user in the user accounts list.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Add Host from which the User can connect</guimenu>:
+ Allows you to specify a host from which the user can connect.
+ This command is unavailable if you highlight a subcategory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Remove Host from which the User can
+ connect</guimenu>: Allows you to remove a host from which the
+ user can connect. If there are no sub-categories, the user
+ will be removed (you will be prompted to confirm the removal).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Clone User</guimenu>: Makes a copy of the selected
+ user, including all subcategories. The new user is called
+ <literal>New User</literal> until you specify another name in
+ the <guilabel>MySQL User</guilabel> field of the
+ <link
+linkend="mysql-administrator-user-administration-user-information">User
+ Information</link> tab. This command is useful for creating
+ users with identical privileges.
+
+ <note>
+ <para>
+ Cloning is only available on Windows.
+ </para>
+ </note>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Delete User</guimenu>: Allows you to delete the
+ selected user. You will be prompted to confirm that you really
+ want to delete that user.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guimenu>Refresh User List</guimenu>: Rereads the user list
+ from the MySQL server. This is helpful when other users (on
+ other connections) are editing user accounts. Note that
+ selecting that command will collapse all subcategories.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section
+id="mysql-administrator-user-administration-user-information">
+
+ <title>User Information</title>
+
+ <para>
+ The fields in this tab are unavailable unless you either click on
+ a username in the
+ <link
+linkend="mysql-administrator-user-administration-user-accounts">User
+ Accounts</link> area of the
+ <link linkend="mysql-administrator-sidebar">sidebar</link>, or
+ create a new user in that sidebar or using the <guibutton>New
+ User</guibutton> button on this tab. In the former case, the
+ fields are filled with the information stored for that user, in
+ the latter case, all fields are empty.
+ </para>
+
+ <para>
+ Note that all fields will be stored only when you click the
+ <guibutton>Apply Changes</guibutton> button. If you don't want to
+ save your changes, click the <guibutton>Discard
+ Changes</guibutton> button.
+ </para>
+
+ <figure>
+ <title>User Information tab</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/user-information.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">User Information tab</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ The values you enter in the fields of this tab are stored on the
+ MySQL server. The fields in the <guilabel>Login
+ Information</guilabel> group of this tab are stored in the
+ <literal>user</literal> table of the <literal>mysql</literal>
+ database, while the fields in the <guilabel>Additional
+ Information</guilabel> group are stored in the
+ <literal>user-info</literal> table of the <literal>mysql</literal>
+ database. The latter table is created the first time you add a new
+ user, or change an existing user. Its contents may look like this:
+ </para>
+
+<programlisting>
+mysql> SELECT * FROM mysql.user-info \G
+ *************************** 1. row ************
+ User: superuser
+ Full-name: Stefan Hinz
+ Description: MySQL Documentation Team
+ Email: stefan@stripped
+ Contact-information: Phone: +49 30 123456789
+ Fax: +49 30 987654321
+ ICQ: 123456789
+ Icon:
+</programlisting>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Login Information
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>MySQL User</guilabel>: Username that is
+ specified when connecting to the MySQL server. Note that
+ this username has nothing to do with usernames you might
+ use elsewhere on your operating system. Using special
+ characters or spaces for a username is not recommended.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Password</guilabel>: Password that is specified
+ when connecting to the MySQL server. Note that this
+ password has nothing to do with passwords you might use
+ elsewhere on your operating system. Again, don't use
+ special characters or spaces for the password. It is,
+ however, recommended that you use non-trivial passwords. A
+ very trivial password might be <literal>abcde</literal>,
+ while a non-trivial password might be
+ <literal>lEtusMak3iThartdoGesz</literal>. Note that it is
+ not mandatory to specify a password, although it is
+ strongly recommended that you do so.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Confirm Password</guilabel>: Fill in the
+ password once again to make sure you do not accidentally
+ introduce a typo.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ Additional Information
+ </para>
+
+ <para>
+ All information specified here is optional.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>Full Name</guilabel>: As opposed to the username
+ in <guilabel>MySQL User</guilabel>, the full name may
+ contain any characters, including spaces.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Description</guilabel>: Additional description
+ of user.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Email</guilabel>: Email address of user.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Contact Information</guilabel>: More contact
+ information, like postal address, or messenger
+ information.
+
+ <remark>
+ [SH] Mike: messager –> messenger
+ </remark>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>Icon</guilabel>: Rather than using the default
+ icon, you may select a different icon by pressing the
+ <guibutton>Load from Disk</guibutton> button.
+
+ <remark>
+ [SH] Mike: In which directory?
+ </remark>
+
+ The icon you use must be exactly 48 by 48 pixels in size,
+ and its file format must be <literal>PNG</literal>
+ (portable network graphics).
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- User Information -->
+
+ <section
+id="mysql-administrator-user-administration-global-privileges">
+
+ <title>Global Privileges</title>
+
+ <para>
+ This tab is available only if the <guilabel>Show Global
+ Privileges</guilabel> checkbox in the
+ <link
+linkend="mysql-gui-options-administrator">Administrator
+ section of the Options dialog</link> has been checked.
+ </para>
+
+ <para>
+ Under <guilabel>Assigned Privileges</guilabel>, you find the
+ global privileges assigned to the selected user. For more
+ information about those privileges, see
+ <xref linkend="privileges-provided"/>. <emphasis>Global</emphasis>
+ means that those privileges apply to the MySQL server in general
+ (like the <literal>Shutdown</literal> privilege), or to all
+ databases on the server (like the <literal>SELECT</literal>
+ privilege).
+ </para>
+
+ <para>
+ Privileges not assigned to the user are listed under
+ <guilabel>Available Privileges</guilabel>. You can remove
+ privileges by selecting them in the left box, and then clicking
+ the <guibutton> > </guibutton> button. Removed privileges will
+ appear in the <guilabel>Available Privileges</guilabel> box. You
+ can assign privileges by selecting them in the <guilabel>Available
+ Privileges</guilabel> box, and then clicking the <guibutton> <
+ </guibutton> button.
+ </para>
+
+ </section>
+
+<!-- Global Privileges -->
+
+ <section
+id="mysql-administrator-user-administration-schema-privileges">
+
+ <title>Schema Privileges</title>
+
+ <para>
+ This tab allows you to grant privileges on a schema level. In
+ MySQL, a schema is the same as a database. To grant privileges for
+ a specific database, click on the database name in the left box.
+ (You cannot select more than one database at a time.)
+ </para>
+
+ <para>
+ You may use wild cards to grant privileges on a number of schemata
+ simultaneously. Use <quote><literal>%</literal></quote> to replace
+ multiple characters and <quote><literal>_</literal></quote> to
+ replace a single character. To use this feature, right click any
+ database name in the schemata list, choose the <guimenu>Add Schema
+ with Wildcards</guimenu> option from the pop-up menu and enter the
+ pattern you wish to match. Entering <literal>m%</literal> for
+ example, will add the entry, <literal>m%</literal> to the schemata
+ list. Highlight this entry and any privileges granted will be
+ granted for all schemata starting with the letter
+ <quote><literal>m</literal></quote>.
+ </para>
+
+ <note>
+ <para>
+ This pop-up menu option is only available under Windows.
+ </para>
+
+ <para>
+ If wild card characters appear in schemata names, you may escape
+ them using the <quote><literal>\</literal></quote> character.
+ </para>
+ </note>
+
+ <para>
+ Privileges not assigned to the user are listed under
+ <guilabel>Available Privileges</guilabel>. You can remove
+ privileges by selecting them in the left box, and then clicking
+ the <guibutton> > </guibutton> button. Removed privileges will
+ appear in the <guilabel>Available Privileges</guilabel> box. You
+ can assign privileges by selecting them in the <guilabel>Available
+ Privileges</guilabel> box, and then clicking the <guibutton> <
+ </guibutton> button.
+ </para>
+
+ <para>
+ The <guilabel>Schema Privileges</guilabel> tab only displays
+ privileges that have been granted for a specific schema. No schema
+ privileges will show in the <guilabel>Assigned
+ Privileges</guilabel> column for users with global privileges. For
+ example, the <guilabel>Assigned Privileges</guilabel> column will
+ be blank for a <literal>root</literal> user with global privileges
+ on all schemata. Likewise, the <guilabel>Assigned
+ Privileges</guilabel> column will be blank for a user with a
+ global <literal>SELECT</literal> privilege, unless
+ <literal>SELECT</literal> has also specifically been granted for
+ the currently selected schema.
+ </para>
+
+ </section>
+
+<!-- Schema Privileges -->
+
+ <section
+id="mysql-administrator-user-administration-table-column-privileges"
+>
+
+ <title>Table Column Privileges</title>
+
+ <para>
+ This tab is available only if the <guilabel>Show Schema Object
+ Privileges</guilabel> checkbox in the
+ <link
+linkend="mysql-gui-options-administrator">Administrator
+ section of the Options dialog</link> has been checked. It allows
+ you to grant privileges on a table level or on a column level.
+ </para>
+
+ <para>
+ To access the tables, double click on the schema (database) name
+ containing that table. You will not see and cannot grant
+ privileges on a schema level in this tab; if you want to do that,
+ use the
+ <link
+linkend="mysql-administrator-user-administration-global-privileges">Global
+ Privileges</link> tab instead. Also, you cannot select more than
+ one table at a time.
+ </para>
+
+<!--para>
+ You may use wild cards to grant privileges on a number of tables or objects
+ simultaneously. Use <quote><literal>%</literal></quote> to replace
+ multiple characters and <quote><literal>_</literal></quote> to replace a
+ single character. To use this feature, right click any database name
+ in the schemata list, choose the <guimenu>Add Schema with Wildcards</guimenu>
+ option and enter the pattern you wish to match. Entering
+ <literal>m%</literal> for example, will add the entry,
+ <literal>m%</literal> to the schemata list. Highlight this entry
+ and any privileges granted will be granted for all schemata starting
+ with the letter <quote><literal>m</literal></quote>.
+ </para>
+
+ <note>
+ <para>
+ This pop-up menu option is only available under Windows.
+ </para>
+ </note-->
+
+ <para>
+ If you want to grant privileges on a column level, double click on
+ the table name; this will give you access to its columns. You
+ cannot select more than one column at a time.
+ </para>
+
+ <para>
+ Privileges not assigned to the user are listed under
+ <guilabel>Available Privileges</guilabel>. You can remove
+ privileges by selecting them in the left box, and then clicking
+ the <guibutton> > </guibutton> button. Removed privileges will
+ appear in the <guilabel>Available Privileges</guilabel> box. You
+ can assign privileges by selecting them in the <guilabel>Available
+ Privileges</guilabel> box, and then clicking the <guibutton> <
+ </guibutton> button.
+ </para>
+
+ </section>
+
+<!-- Table Column Privileges -->
+
+<!--
+ <section id="mysql-administrator-user-administration-administrator">
+ <title>Resources</title>
+ <para>
+ This tab allows you to limit user administrator. Note that this is
+available as of MySQL 4.0.2 only. If the values in this tab are set
+to <literal>0</literal>, this means that user administrator are not
+limited. Setting them to a non-zero value limits the user administrator
+per hour:
+ <itemizedlist>
+ <listitem><para>
+ <literal>max-questions</literal>: Number of queries (commands) the
+user can send to the server.
+ </para></listitem>
+ <listitem><para>
+ <literal>max-updates</literal>: Number of updates the user can send
+to the server.
+ </para></listitem>
+ <listitem><para>
+ <literal>max-connections</literal>: Number of connections the user
+can make to the server.
+ </para></listitem>
+ </itemizedlist>
+ For more information about limiting user administrator, see <xref linkend="user-administrator"/>
+ </para>
+ </section> Resources
+-->
+
+ <section id="administrator-resources">
+
+ <title>Resources</title>
+
+ <para>
+ This tab allows you to limit a user's resources. You may set
+ limits for the following items:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <guilabel>max_questions</guilabel> – The number of
+ questions allowed per hour
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>max_update</guilabel> – The number of updates
+ allowed per hour
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>max_connections</guilabel> – The number of
+ connections allowed per hour
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <guilabel>max_user_connections</guilabel> – The number
+ of simultaneous connections allowed
+ </para>
+
+ <note>
+ <para>
+ This option is only available under Windows
+ </para>
+ </note>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The default value for each of these settings is
+ <literal>0</literal>, indicating no restrictions whatsoever.
+ </para>
+
+ </section>
+
+</chapter>
Added: trunk/th/administrator/xml-files.xml
===================================================================
--- trunk/th/administrator/xml-files.xml (rev 0)
+++ trunk/th/administrator/xml-files.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 186, Lines Deleted: 0; 6941 bytes
@@ -0,0 +1,186 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<appendix id="mysql-administrator-appendix-xml-files">
+
+ <title>XML Files Used by &administrator;</title>
+
+ <para>
+ Besides the documentation you are currently reading (which is
+ written in DocBook XML), &administrator; uses a number of XML files
+ for internal purposes.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <filename>mysqlx-options.xml</filename>: Stores options selected
+ in the <link
+ linkend="mysql-gui-options">Options
+ dialog</link>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqlx-status-variables.xml</filename>: Stores the
+ status variables known to &administrator;, so that they can be
+ assigned descriptions in various languages (see below for the
+ XML file containing those descriptions). Those descriptions will
+ show up in the
+ <link linkend="mysql-administrator-health-status-variables">Status
+ Variables</link> tab of the
+ <link linkend="mysql-administrator-health">Health</link>
+ section. You can select the language of the descriptions in the
+ <link linkend="mysql-gui-options-general-options">General
+ Options</link> section of the
+ <link linkend="mysql-gui-options">Options dialog</link>. That
+ file also determines in which categories or subcategories a
+ variable will appear, and the order in which categories and
+ subcategories appear. However, it does not determine the order
+ of variables within a category or subcategory, as these are
+ sorted lexically by &administrator;.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqlx-system-variables.xml</filename>: Stores the
+ system variables known to &administrator;, so that they can be
+ assigned descriptions in various languages (see below for the
+ XML file containing those descriptions). Those descriptions will
+ show up in the
+ <link linkend="mysql-administrator-health-system-variables">System
+ Variables</link> tab of the
+ <link linkend="mysql-administrator-health">Health</link>
+ section. You can select the language of the descriptions in the
+ <link linkend="mysql-gui-options-general-options">General
+ Options</link> section of the
+ <link linkend="mysql-gui-options">Options dialog</link>. That
+ file also determines in which categories or subcategories a
+ variable will appear, and the order in which categories and
+ subcategories appear. However, it does not determine the order
+ of variables within a category or subcategory, as these are
+ sorted lexically by &administrator;.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqlx-translations-administrator.xml</filename> :
+ Stores descriptions specific to &administrator;, like
+ descriptions for status and server variables, or category names,
+ or labels used in dialogs. Here is an excerpt from that file,
+ which contains English and German texts:
+ </para>
+
+<programlisting>
+ <textgroup id="MySQLVariables">
+ <text id="status-var-group-General">
+ <trans xml:lang="en">General</trans>
+ <trans xml:lang="de">Allgemein</trans>
+ </text>
+ <text id="status-var-Uptime">
+ <trans xml:lang="en">How many seconds the server has been
+up.</trans>
+ </text>
+ ...
+ <textgroup id="Form-InstanceForm">
+ <text id="FileMI">
+ <trans xml:lang="en">&File</trans>
+ <trans xml:lang="de">&Datei</trans>
+ </text>
+ <text id="NewConnectionMI">
+ <trans xml:lang="en">&New Connection
+...</trans>
+ <trans xml:lang="de">&Neue Verbindung
+...</trans>
+ </text>
+ <text id="SaveConnectionMI">
+ <trans xml:lang="en">&Save Connection
+...</trans>
+ <trans xml:lang="de">Verbindung &speichern
+...</trans>
+ </text>
+ <text id="CloseMI">
+ <trans xml:lang="en">Clos&e</trans>
+ <trans xml:lang="de">Be&enden</trans>
+ </text>
+ </textgroup>
+ ...
+ </programlisting>
+
+ <para>
+ This excerpt demonstrates a number of things:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ A description (called <emphasis>text</emphasis>) does not
+ necessarily have to be translated (see
+ <literal>status-var-Uptime</literal>). If there is no
+ translation, English will be used instead.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Adding another translation is as simple as adding another
+ <literal><trans
+ xml:lang="<replaceable>language</replaceable>"></literal>
+ tag.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Consequently, translating the software is a relatively painless
+ task; however, please look at the
+ <link linkend="mysql-gui-appendix-notes-for-translators">Notes
+ for Translators</link> below.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqlx-translations-general.xml</filename>: Stores
+ terms and descriptions that appear not only in &administrator;,
+ but also in other graphical MySQL programs. Its format, however,
+ is identical with the format of the
+ <filename>mysqlx-translations-administrator.xml</filename> file.
+ Here is an excerpt from that file:
+ </para>
+
+<programlisting>
+<textgroup id="ResourceStrings">
+ <text id="OKBtn">
+ <trans xml:lang="en">OK</trans>
+ </text>
+ <text id="CancelBtn">
+ <trans xml:lang="en">Cancel</trans>
+ <trans xml:lang="de">Abbruch</trans>
+ </text>
+ ...
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqlx-user-connections.xml</filename>: This file is
+ described in
+ <link linkend="mysql-gui-appendix-store-connections">How
+ &administrator; Stores Connections</link>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+</appendix>
Added: trunk/th/common/fixedchars.ent
===================================================================
--- trunk/th/common/fixedchars.ent (rev 0)
+++ trunk/th/common/fixedchars.ent 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 249, Lines Deleted: 0; 9323 bytes
@@ -0,0 +1,249 @@
+ <!ENTITY minus "–"> <!-- 2013 is actually Unicode for ndash -->
+ <!ENTITY Oslash "Ø">
+ <!ENTITY macr "¯">
+ <!ENTITY auml "ä">
+ <!ENTITY ouml "ö">
+ <!ENTITY uuml "ü">
+ <!ENTITY Auml "Ä">
+ <!ENTITY Ouml "Ö">
+ <!ENTITY Uuml "Ü">
+ <!ENTITY aring "å">
+ <!ENTITY szlig "ß">
+ <!ENTITY copy "©">
+ <!ENTITY Acirc "Â">
+ <!ENTITY acirc "â">
+ <!ENTITY oslash "ø">
+ <!ENTITY otilde "õ">
+ <!ENTITY oacute "ó">
+ <!ENTITY eacute "é">
+ <!ENTITY aacute "á">
+ <!ENTITY Aacute "Á">
+ <!ENTITY acirc "â">
+ <!ENTITY Acirc "Â">
+ <!ENTITY agrave "à">
+ <!ENTITY Agrave "À">
+ <!ENTITY aring "å">
+ <!ENTITY Aring "Å">
+ <!ENTITY atilde "ã">
+ <!ENTITY Atilde "Ã">
+ <!ENTITY auml "ä">
+ <!ENTITY Auml "Ä">
+ <!ENTITY aelig "æ">
+ <!ENTITY AElig "Æ">
+ <!ENTITY ccedil "ç">
+ <!ENTITY Ccedil "Ç">
+ <!ENTITY eth "ð">
+ <!ENTITY ETH "Ð">
+ <!ENTITY eacute "é">
+ <!ENTITY Eacute "É">
+ <!ENTITY ecirc "ê">
+ <!ENTITY Ecirc "Ê">
+ <!ENTITY egrave "è">
+ <!ENTITY Egrave "È">
+ <!ENTITY euml "ë">
+ <!ENTITY Euml "Ë">
+ <!ENTITY iacute "í">
+ <!ENTITY Iacute "Í">
+ <!ENTITY icirc "î">
+ <!ENTITY Icirc "Î">
+ <!ENTITY igrave "ì">
+ <!ENTITY Igrave "Ì">
+ <!ENTITY iuml "ï">
+ <!ENTITY Iuml "Ï">
+ <!ENTITY ntilde "ñ">
+ <!ENTITY Ntilde "Ñ">
+ <!ENTITY oacute "ó">
+ <!ENTITY Oacute "Ó">
+ <!ENTITY ocirc "ô">
+ <!ENTITY Ocirc "Ô">
+ <!ENTITY ograve "ò">
+ <!ENTITY Ograve "Ò">
+ <!ENTITY oslash "ø">
+ <!ENTITY Oslash "Ø">
+ <!ENTITY otilde "õ">
+ <!ENTITY Otilde "Õ">
+ <!ENTITY ouml "ö">
+ <!ENTITY Ouml "Ö">
+ <!ENTITY szlig "ß">
+ <!ENTITY thorn "þ">
+ <!ENTITY THORN "Þ">
+ <!ENTITY uacute "ú">
+ <!ENTITY Uacute "Ú">
+ <!ENTITY ucirc "û">
+ <!ENTITY Ucirc "Û">
+ <!ENTITY ugrave "ù">
+ <!ENTITY Ugrave "Ù">
+ <!ENTITY uuml "ü">
+ <!ENTITY Uuml "Ü">
+ <!ENTITY yacute "ý">
+ <!ENTITY Yacute "Ý">
+ <!ENTITY yuml "ÿ">
+ <!ENTITY half "½">
+ <!ENTITY frac12 "½">
+ <!ENTITY frac14 "¼">
+ <!ENTITY frac34 "¾">
+ <!ENTITY frac18 "⅛">
+ <!ENTITY frac38 "⅜">
+ <!ENTITY frac58 "⅝">
+ <!ENTITY frac78 "⅞">
+ <!ENTITY sup1 "¹">
+ <!ENTITY sup2 "²">
+ <!ENTITY sup3 "³">
+ <!ENTITY plus "+">
+ <!ENTITY plusmn "±">
+ <!ENTITY lt "&#60;">
+ <!ENTITY equals "=">
+ <!ENTITY gt ">">
+ <!ENTITY divide "÷">
+ <!ENTITY times "×">
+ <!ENTITY curren "¤">
+ <!ENTITY pound "£">
+ <!ENTITY dollar "$">
+ <!ENTITY cent "¢">
+ <!ENTITY yen "¥">
+ <!ENTITY num "#">
+ <!ENTITY percnt "%">
+ <!ENTITY amp "&#38;">
+ <!ENTITY ast "*">
+ <!ENTITY commat "@">
+ <!ENTITY lsqb "[">
+ <!ENTITY bsol "\">
+ <!ENTITY rsqb "]">
+ <!ENTITY lcub "{">
+ <!ENTITY horbar "―">
+ <!ENTITY verbar "|">
+ <!ENTITY rcub "}">
+ <!ENTITY micro "µ">
+ <!ENTITY ohm "Ω">
+ <!ENTITY deg "°">
+ <!ENTITY ordm "º">
+ <!ENTITY ordf "ª">
+ <!ENTITY sect "§">
+ <!ENTITY para "¶">
+ <!ENTITY middot "·">
+ <!ENTITY larr "←">
+ <!ENTITY rarr "→">
+ <!ENTITY uarr "↑">
+ <!ENTITY darr "↓">
+ <!ENTITY copy "©">
+ <!ENTITY reg "®">
+ <!ENTITY trade "™">
+ <!ENTITY brvbar "¦">
+ <!ENTITY not "¬">
+ <!ENTITY sung "♩">
+ <!ENTITY excl "!">
+ <!ENTITY iexcl "¡">
+ <!ENTITY quot """>
+ <!ENTITY apos "'">
+ <!ENTITY lpar "(">
+ <!ENTITY rpar ")">
+ <!ENTITY comma ",">
+ <!ENTITY lowbar "_">
+ <!ENTITY hyphen "-">
+ <!ENTITY period ".">
+ <!ENTITY sol "/">
+ <!ENTITY colon ":">
+ <!ENTITY semi ";">
+ <!ENTITY quest "?">
+ <!ENTITY iquest "¿">
+ <!ENTITY laquo "«">
+ <!ENTITY raquo "»">
+ <!ENTITY lsquo "‘">
+ <!ENTITY rsquo "’">
+ <!ENTITY ldquo "“">
+ <!ENTITY rdquo "”">
+ <!ENTITY nbsp " ">
+ <!ENTITY shy "­">
+ <!ENTITY emsp " ">
+ <!ENTITY ensp " ">
+ <!ENTITY emsp13 " ">
+ <!ENTITY emsp14 " ">
+ <!ENTITY numsp " ">
+ <!ENTITY puncsp " ">
+ <!ENTITY thinsp " ">
+ <!ENTITY hairsp " ">
+ <!ENTITY mdash "—">
+ <!ENTITY ndash "–">
+ <!ENTITY dash "‐">
+ <!ENTITY blank "␣">
+ <!ENTITY hellip "…">
+ <!ENTITY nldr "‥">
+ <!ENTITY frac13 "⅓">
+ <!ENTITY frac23 "⅔">
+ <!ENTITY frac15 "⅕">
+ <!ENTITY frac25 "⅖">
+ <!ENTITY frac35 "⅗">
+ <!ENTITY frac45 "⅘">
+ <!ENTITY frac16 "⅙">
+ <!ENTITY frac56 "⅚">
+ <!ENTITY incare "℅">
+ <!ENTITY block "█">
+ <!ENTITY uhblk "▀">
+ <!ENTITY lhblk "▄">
+ <!ENTITY blk14 "░">
+ <!ENTITY blk12 "▒">
+ <!ENTITY blk34 "▓">
+ <!ENTITY marker "▮">
+ <!ENTITY cir "○">
+ <!ENTITY squ "□">
+ <!ENTITY rect "▭">
+ <!ENTITY utri "▵">
+ <!ENTITY dtri "▿">
+ <!ENTITY star "⋆">
+ <!ENTITY bull "•">
+ <!ENTITY squf "▪">
+ <!ENTITY utrif "▴">
+ <!ENTITY dtrif "▾">
+ <!ENTITY ltrif "◂">
+ <!ENTITY rtrif "▸">
+ <!ENTITY clubs "♣">
+ <!ENTITY diams "♦">
+ <!ENTITY hearts "♥">
+ <!ENTITY spades "♠">
+ <!ENTITY malt "✠">
+ <!ENTITY dagger "†">
+ <!ENTITY Dagger "‡">
+ <!ENTITY check "✓">
+ <!ENTITY cross "✗">
+ <!ENTITY sharp "♯">
+ <!ENTITY flat "♭">
+ <!ENTITY male "♂">
+ <!ENTITY female "♀">
+ <!ENTITY phone "☎">
+ <!ENTITY telrec "⌕">
+ <!ENTITY copysr "℗">
+ <!ENTITY caret "⁁">
+ <!ENTITY lsquor "‚">
+ <!ENTITY ldquor "„">
+ <!ENTITY fflig "ff">
+ <!ENTITY filig "fi">
+ <!ENTITY ffilig "ffi">
+ <!ENTITY ffllig "ffl">
+ <!ENTITY fllig "fl">
+ <!ENTITY mldr "…">
+ <!ENTITY rdquor "“">
+ <!ENTITY rsquor "‘">
+ <!ENTITY vellip "⋮">
+ <!ENTITY hybull "⁃">
+ <!ENTITY loz "◊">
+ <!ENTITY lozf "✦">
+ <!ENTITY ltri "◃">
+ <!ENTITY rtri "▹">
+ <!ENTITY starf "★">
+ <!ENTITY natur "♮">
+ <!ENTITY rx "℞">
+ <!ENTITY sext "✶">
+ <!ENTITY target "⌖">
+ <!ENTITY dlcrop "⌍">
+ <!ENTITY drcrop "⌌">
+ <!ENTITY ulcrop "⌏">
+ <!ENTITY urcrop "⌎">
+ <!ENTITY pi "π">
+ <!ENTITY euro "€">
+ <!ENTITY le "≤">
+ <!ENTITY ge "≥">
+ <!ENTITY ddash "--">
+ <!ENTITY dArr "⇓"> <!-- DOWNWARDS DOUBLE ARROW -->
+ <!ENTITY uArr "⇑"> <!-- UPWARDS DOUBLE ARROW -->
+ <!ENTITY vArr "⇕"> <!-- UP DOWN DOUBLE ARROW -->
+ <!ENTITY mu "μ"> <!-- GREEK LETTER MU -->
Added: trunk/th/common/phrases.ent
===================================================================
--- trunk/th/common/phrases.ent (rev 0)
+++ trunk/th/common/phrases.ent 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 25, Lines Deleted: 0; 4101 bytes
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+ This file contains commonly used phrases.
+-->
+
+<!ENTITY answers 'Answers'>
+<!ENTITY cs-only '<para role="cs">This section does not apply to MySQL Enterprise Server users.</para>'>
+<!ENTITY deprecated-feature-warning '<para role="deprecated"><emphasis role="bold">This feature is deprecated. We recommend not using it anymore. It is subject to removal in a future version of MySQL.</emphasis></para>'>
+<!ENTITY eol-warning '<formalpara role="depnote"><title>End of Product Lifecycle</title><para>Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see <ulink url="http://www.mysql.com/company/legal/lifecycle/#calendar"/>. According to the MySQL Lifecycle Policy (see <ulink url="http://www.mysql.com/company/legal/lifecycle/#policy"/>), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).</para></formalpara>'>
+<!ENTITY enterprise-offering-note '<para>This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized <emphasis>update alerts</emphasis> about fixes that are relevant to the version and features you use, please consider subscribing to <emphasis>MySQL Enterprise</emphasis> (a commercial MySQL offering). For more details please see <ulink url="http://www.mysql.com/products/enterprise"/>.</para>'>
+<!ENTITY es-only '<para role="es">This section does not apply to MySQL Community Server users.</para>'>
+<!ENTITY falcon-warning '<para role="deprecated"><emphasis role="bold">Falcon support is not available in the standard MySQL 5.1 release. Falcon is available only in a specially forked release of MySQL 5.1. Information is provided here for evaluation purposes only.</emphasis></para>'>
+<!ENTITY questions 'Questions'>
+<!ENTITY questionsandanswers 'Questions and Answers'>
+
+<!-- Specific to MCCGE, used in 5.1/5.2 Manual and Cluster API docs -->
+<!ENTITY mccge-series "MySQL Cluster ¤t-series; Carrier Grade Edition">
+<!ENTITY mccge-current "5.1.15-ndb-6.1.6-beta"><!-- Current MySQL CGE version - update with new releases -->
+<!ENTITY mccge-warning-section '<formalpara role="mccge-warning"><title>&mccge-series;</title><para>The information in this section applies to users of &mccge-series; only. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
+<!ENTITY mccge-warning-begin '<formalpara role="mccge-warning"><title>&mccge-series;</title><para>The following information applies to users of &mccge-series; only. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
+<!ENTITY mccge-warning-end-api '<para role="mccge-warning">The following information applies to all MySQL Cluster API users.</para>'>
+<!ENTITY mccge-warning-end-cluster '<para role="mccge-warning">The following information applies to all MySQL Cluster users.</para>'>
+<!ENTITY mccge-warning-end-all '<para role="mccge-warning">The following information applies to all MySQL users.</para>'>
+<!ENTITY mccge-warning-section-unsupported '<formalpara role="mccge-warning"><title>&mccge-series;</title><para>The information in this section does not apply to users of &mccge-series;. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
+<!ENTITY mccge-warning-unsupported-begin '<formalpara role="mccge-warning"><title>&mccge-series;</title><para>The following information does not apply to users of &mccge-series;. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
Added: trunk/th/gui-common/Makefile
===================================================================
--- trunk/th/gui-common/Makefile (rev 0)
+++ trunk/th/gui-common/Makefile 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 46, Lines Deleted: 0; 1416 bytes
@@ -0,0 +1,46 @@
+# Makefile for MySQL Reference Manual
+
+# Location of repository root relative to current directory
+REPO_ROOT = ..
+
+# Location of directory containing Makefile components
+MAKE_DIR = $(REPO_ROOT)/make.d
+
+# Set any variables here that should override imported standard variables
+
+DOC_LANG = en
+MAIN_DOC_BASENAME = gui-common
+
+# Set IDMAP and remap variables
+
+IDMAP_LANG = $(DOC_LANG)
+IDMAP_MAIN = gui-common
+
+IDMAP_URLBASE = $(IDMAP_MAIN)/$(IDMAP_LANG)
+IDMAP_REFS = . $(REPO_ROOT)/administrator $(REPO_ROOT)/migration-toolkit $(REPO_ROOT)/refman-5.1 $(REPO_ROOT)/refman-common
+IDMAP_SRCS = $(call base_xml_files)
+
+# Import standard variables
+
+include $(MAKE_DIR)/vars-layout
+include $(MAKE_DIR)/vars-shell
+include $(MAKE_DIR)/vars-docbook
+
+# Import default target rule (causes help message to print)
+
+include $(MAKE_DIR)/default-target
+
+# Files for which to generate dependencies
+DEPEND_FILES = $(wildcard *.xml)
+
+# Import document dependency specifications
+
+include Makefile.depends
+
+# Import standard target rules
+
+include $(MAKE_DIR)/xml-valid
+include $(MAKE_DIR)/xml-format
+include $(MAKE_DIR)/xml-prep
+include $(MAKE_DIR)/xml-useless
+include $(MAKE_DIR)/xml-depend
Added: trunk/th/gui-common/Makefile.depends
===================================================================
--- trunk/th/gui-common/Makefile.depends (rev 0)
+++ trunk/th/gui-common/Makefile.depends 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 303, Lines Deleted: 0; 18058 bytes
@@ -0,0 +1,303 @@
+appendix_common_files_INCLUDES =
+appendix_common_files_IMAGES =
+appendix_common_files_SOURCES = appendix-common-files.xml $(appendix_common_files_INCLUDES)
+appendix_common_files_IDMAPS = \
+ ../administrator/metadata/administrator.idmap \
+ metadata/appendix-connection-storage.idmap
+appendix-common-files.validpure: $(appendix_common_files_SOURCES)
+appendix-common-files.titles: $(appendix_common_files_SOURCES)
+appendix-common-files.useless: $(appendix_common_files_SOURCES)
+appendix-common-files.valid: $(appendix_common_files_SOURCES) $(appendix_common_files_IDMAPS)
+appendix-common-files.validwarn: $(appendix_common_files_SOURCES) $(appendix_common_files_IDMAPS)
+appendix-common-files-prepped.xml: $(appendix_common_files_SOURCES) $(appendix_common_files_IDMAPS)
+appendix-common-files-manprepped.xml: $(appendix_common_files_SOURCES) $(appendix_common_files_IDMAPS)
+appendix-common-files-remprepped.xml: $(appendix_common_files_SOURCES) $(appendix_common_files_IDMAPS)
+
+appendix_connection_storage_INCLUDES =
+appendix_connection_storage_IMAGES =
+appendix_connection_storage_SOURCES = appendix-connection-storage.xml $(appendix_connection_storage_INCLUDES)
+appendix_connection_storage_IDMAPS = \
+ ../administrator/metadata/administrator.idmap \
+ metadata/chapter-options-connections.idmap
+appendix-connection-storage.validpure: $(appendix_connection_storage_SOURCES)
+appendix-connection-storage.titles: $(appendix_connection_storage_SOURCES)
+appendix-connection-storage.useless: $(appendix_connection_storage_SOURCES)
+appendix-connection-storage.valid: $(appendix_connection_storage_SOURCES) $(appendix_connection_storage_IDMAPS)
+appendix-connection-storage.validwarn: $(appendix_connection_storage_SOURCES) $(appendix_connection_storage_IDMAPS)
+appendix-connection-storage-prepped.xml: $(appendix_connection_storage_SOURCES) $(appendix_connection_storage_IDMAPS)
+appendix-connection-storage-manprepped.xml: $(appendix_connection_storage_SOURCES) $(appendix_connection_storage_IDMAPS)
+appendix-connection-storage-remprepped.xml: $(appendix_connection_storage_SOURCES) $(appendix_connection_storage_IDMAPS)
+
+appendix_source_install_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+appendix_source_install_IMAGES =
+appendix_source_install_SOURCES = appendix-source-install.xml $(appendix_source_install_INCLUDES)
+appendix_source_install_IDMAPS =
+appendix-source-install.validpure: $(appendix_source_install_SOURCES)
+appendix-source-install.titles: $(appendix_source_install_SOURCES)
+appendix-source-install.useless: $(appendix_source_install_SOURCES)
+appendix-source-install.valid: $(appendix_source_install_SOURCES) $(appendix_source_install_IDMAPS)
+appendix-source-install.validwarn: $(appendix_source_install_SOURCES) $(appendix_source_install_IDMAPS)
+appendix-source-install-prepped.xml: $(appendix_source_install_SOURCES) $(appendix_source_install_IDMAPS)
+appendix-source-install-manprepped.xml: $(appendix_source_install_SOURCES) $(appendix_source_install_IDMAPS)
+appendix-source-install-remprepped.xml: $(appendix_source_install_SOURCES) $(appendix_source_install_IDMAPS)
+
+appendix_third_party_INCLUDES =
+appendix_third_party_IMAGES =
+appendix_third_party_SOURCES = appendix-third-party.xml $(appendix_third_party_INCLUDES)
+appendix_third_party_IDMAPS =
+appendix-third-party.validpure: $(appendix_third_party_SOURCES)
+appendix-third-party.titles: $(appendix_third_party_SOURCES)
+appendix-third-party.useless: $(appendix_third_party_SOURCES)
+appendix-third-party.valid: $(appendix_third_party_SOURCES) $(appendix_third_party_IDMAPS)
+appendix-third-party.validwarn: $(appendix_third_party_SOURCES) $(appendix_third_party_IDMAPS)
+appendix-third-party-prepped.xml: $(appendix_third_party_SOURCES) $(appendix_third_party_IDMAPS)
+appendix-third-party-manprepped.xml: $(appendix_third_party_SOURCES) $(appendix_third_party_IDMAPS)
+appendix-third-party-remprepped.xml: $(appendix_third_party_SOURCES) $(appendix_third_party_IDMAPS)
+
+appendix_translator_notes_INCLUDES =
+appendix_translator_notes_IMAGES =
+appendix_translator_notes_SOURCES = appendix-translator-notes.xml $(appendix_translator_notes_INCLUDES)
+appendix_translator_notes_IDMAPS =
+appendix-translator-notes.validpure: $(appendix_translator_notes_SOURCES)
+appendix-translator-notes.titles: $(appendix_translator_notes_SOURCES)
+appendix-translator-notes.useless: $(appendix_translator_notes_SOURCES)
+appendix-translator-notes.valid: $(appendix_translator_notes_SOURCES) $(appendix_translator_notes_IDMAPS)
+appendix-translator-notes.validwarn: $(appendix_translator_notes_SOURCES) $(appendix_translator_notes_IDMAPS)
+appendix-translator-notes-prepped.xml: $(appendix_translator_notes_SOURCES) $(appendix_translator_notes_IDMAPS)
+appendix-translator-notes-manprepped.xml: $(appendix_translator_notes_SOURCES) $(appendix_translator_notes_IDMAPS)
+appendix-translator-notes-remprepped.xml: $(appendix_translator_notes_SOURCES) $(appendix_translator_notes_IDMAPS)
+
+appendix_troubleshooting_INCLUDES = \
+ images/published/connectionerror.png
+appendix_troubleshooting_IMAGES = \
+ images/published/connectionerror.png
+appendix_troubleshooting_SOURCES = appendix-troubleshooting.xml $(appendix_troubleshooting_INCLUDES)
+appendix_troubleshooting_IDMAPS = \
+ ../refman-5.1/metadata/dba-core.idmap
+appendix-troubleshooting.validpure: $(appendix_troubleshooting_SOURCES)
+appendix-troubleshooting.titles: $(appendix_troubleshooting_SOURCES)
+appendix-troubleshooting.useless: $(appendix_troubleshooting_SOURCES)
+appendix-troubleshooting.valid: $(appendix_troubleshooting_SOURCES) $(appendix_troubleshooting_IDMAPS)
+appendix-troubleshooting.validwarn: $(appendix_troubleshooting_SOURCES) $(appendix_troubleshooting_IDMAPS)
+appendix-troubleshooting-prepped.xml: $(appendix_troubleshooting_SOURCES) $(appendix_troubleshooting_IDMAPS)
+appendix-troubleshooting-manprepped.xml: $(appendix_troubleshooting_SOURCES) $(appendix_troubleshooting_IDMAPS)
+appendix-troubleshooting-remprepped.xml: $(appendix_troubleshooting_SOURCES) $(appendix_troubleshooting_IDMAPS)
+
+chapter_grt_shell_INCLUDES = \
+ ../common/fixedchars.ent \
+ images/published/grt-shell.png
+chapter_grt_shell_IMAGES = \
+ images/published/grt-shell.png
+chapter_grt_shell_SOURCES = chapter-grt-shell.xml $(chapter_grt_shell_INCLUDES)
+chapter_grt_shell_IDMAPS = \
+ ../migration-toolkit/metadata/indepth.idmap \
+ ../migration-toolkit/metadata/scripted-migration.idmap \
+ metadata/chapter-grt-shell.idmap
+chapter-grt-shell.validpure: $(chapter_grt_shell_SOURCES)
+chapter-grt-shell.titles: $(chapter_grt_shell_SOURCES)
+chapter-grt-shell.useless: $(chapter_grt_shell_SOURCES)
+chapter-grt-shell.valid: $(chapter_grt_shell_SOURCES) $(chapter_grt_shell_IDMAPS)
+chapter-grt-shell.validwarn: $(chapter_grt_shell_SOURCES) $(chapter_grt_shell_IDMAPS)
+chapter-grt-shell-prepped.xml: $(chapter_grt_shell_SOURCES) $(chapter_grt_shell_IDMAPS)
+chapter-grt-shell-manprepped.xml: $(chapter_grt_shell_SOURCES) $(chapter_grt_shell_IDMAPS)
+chapter-grt-shell-remprepped.xml: $(chapter_grt_shell_SOURCES) $(chapter_grt_shell_IDMAPS)
+
+chapter_options_connections_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent \
+ images/published/options-connection.png \
+ images/published/ssl-params.png
+chapter_options_connections_IMAGES = \
+ images/published/options-connection.png \
+ images/published/ssl-params.png
+chapter_options_connections_SOURCES = chapter-options-connections.xml $(chapter_options_connections_INCLUDES)
+chapter_options_connections_IDMAPS = \
+ metadata/chapter-options-general.idmap
+chapter-options-connections.validpure: $(chapter_options_connections_SOURCES)
+chapter-options-connections.titles: $(chapter_options_connections_SOURCES)
+chapter-options-connections.useless: $(chapter_options_connections_SOURCES)
+chapter-options-connections.valid: $(chapter_options_connections_SOURCES) $(chapter_options_connections_IDMAPS)
+chapter-options-connections.validwarn: $(chapter_options_connections_SOURCES) $(chapter_options_connections_IDMAPS)
+chapter-options-connections-prepped.xml: $(chapter_options_connections_SOURCES) $(chapter_options_connections_IDMAPS)
+chapter-options-connections-manprepped.xml: $(chapter_options_connections_SOURCES) $(chapter_options_connections_IDMAPS)
+chapter-options-connections-remprepped.xml: $(chapter_options_connections_SOURCES) $(chapter_options_connections_IDMAPS)
+
+chapter_options_editors_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+chapter_options_editors_IMAGES =
+chapter_options_editors_SOURCES = chapter-options-editors.xml $(chapter_options_editors_INCLUDES)
+chapter_options_editors_IDMAPS = \
+ metadata/chapter-table-editor.idmap
+chapter-options-editors.validpure: $(chapter_options_editors_SOURCES)
+chapter-options-editors.titles: $(chapter_options_editors_SOURCES)
+chapter-options-editors.useless: $(chapter_options_editors_SOURCES)
+chapter-options-editors.valid: $(chapter_options_editors_SOURCES) $(chapter_options_editors_IDMAPS)
+chapter-options-editors.validwarn: $(chapter_options_editors_SOURCES) $(chapter_options_editors_IDMAPS)
+chapter-options-editors-prepped.xml: $(chapter_options_editors_SOURCES) $(chapter_options_editors_IDMAPS)
+chapter-options-editors-manprepped.xml: $(chapter_options_editors_SOURCES) $(chapter_options_editors_IDMAPS)
+chapter-options-editors-remprepped.xml: $(chapter_options_editors_SOURCES) $(chapter_options_editors_IDMAPS)
+
+chapter_options_general_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+chapter_options_general_IMAGES =
+chapter_options_general_SOURCES = chapter-options-general.xml $(chapter_options_general_INCLUDES)
+chapter_options_general_IDMAPS =
+chapter-options-general.validpure: $(chapter_options_general_SOURCES)
+chapter-options-general.titles: $(chapter_options_general_SOURCES)
+chapter-options-general.useless: $(chapter_options_general_SOURCES)
+chapter-options-general.valid: $(chapter_options_general_SOURCES) $(chapter_options_general_IDMAPS)
+chapter-options-general.validwarn: $(chapter_options_general_SOURCES) $(chapter_options_general_IDMAPS)
+chapter-options-general-prepped.xml: $(chapter_options_general_SOURCES) $(chapter_options_general_IDMAPS)
+chapter-options-general-manprepped.xml: $(chapter_options_general_SOURCES) $(chapter_options_general_IDMAPS)
+chapter-options-general-remprepped.xml: $(chapter_options_general_SOURCES) $(chapter_options_general_IDMAPS)
+
+chapter_options_introduction_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent \
+ images/published/options.png
+chapter_options_introduction_IMAGES = \
+ images/published/options.png
+chapter_options_introduction_SOURCES = chapter-options-introduction.xml $(chapter_options_introduction_INCLUDES)
+chapter_options_introduction_IDMAPS =
+chapter-options-introduction.validpure: $(chapter_options_introduction_SOURCES)
+chapter-options-introduction.titles: $(chapter_options_introduction_SOURCES)
+chapter-options-introduction.useless: $(chapter_options_introduction_SOURCES)
+chapter-options-introduction.valid: $(chapter_options_introduction_SOURCES) $(chapter_options_introduction_IDMAPS)
+chapter-options-introduction.validwarn: $(chapter_options_introduction_SOURCES) $(chapter_options_introduction_IDMAPS)
+chapter-options-introduction-prepped.xml: $(chapter_options_introduction_SOURCES) $(chapter_options_introduction_IDMAPS)
+chapter-options-introduction-manprepped.xml: $(chapter_options_introduction_SOURCES) $(chapter_options_introduction_IDMAPS)
+chapter-options-introduction-remprepped.xml: $(chapter_options_introduction_SOURCES) $(chapter_options_introduction_IDMAPS)
+
+chapter_table_editor_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent \
+ images/published/columneditor.png \
+ images/published/confirmchanges.png \
+ images/published/indexeditor.png \
+ images/published/tableeditor.png
+chapter_table_editor_IMAGES = \
+ images/published/columneditor.png \
+ images/published/confirmchanges.png \
+ images/published/indexeditor.png \
+ images/published/tableeditor.png
+chapter_table_editor_SOURCES = chapter-table-editor.xml $(chapter_table_editor_INCLUDES)
+chapter_table_editor_IDMAPS = \
+ ../refman-5.1/metadata/se-merge.idmap \
+ ../refman-5.1/metadata/se-myisam.idmap \
+ ../refman-5.1/metadata/sql-syntax.idmap \
+ metadata/chapter-options-editors.idmap \
+ metadata/chapter-table-editor.idmap
+chapter-table-editor.validpure: $(chapter_table_editor_SOURCES)
+chapter-table-editor.titles: $(chapter_table_editor_SOURCES)
+chapter-table-editor.useless: $(chapter_table_editor_SOURCES)
+chapter-table-editor.valid: $(chapter_table_editor_SOURCES) $(chapter_table_editor_IDMAPS)
+chapter-table-editor.validwarn: $(chapter_table_editor_SOURCES) $(chapter_table_editor_IDMAPS)
+chapter-table-editor-prepped.xml: $(chapter_table_editor_SOURCES) $(chapter_table_editor_IDMAPS)
+chapter-table-editor-manprepped.xml: $(chapter_table_editor_SOURCES) $(chapter_table_editor_IDMAPS)
+chapter-table-editor-remprepped.xml: $(chapter_table_editor_SOURCES) $(chapter_table_editor_IDMAPS)
+
+chapter_uninstall_all_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+chapter_uninstall_all_IMAGES =
+chapter_uninstall_all_SOURCES = chapter-uninstall-all.xml $(chapter_uninstall_all_INCLUDES)
+chapter_uninstall_all_IDMAPS =
+chapter-uninstall-all.validpure: $(chapter_uninstall_all_SOURCES)
+chapter-uninstall-all.titles: $(chapter_uninstall_all_SOURCES)
+chapter-uninstall-all.useless: $(chapter_uninstall_all_SOURCES)
+chapter-uninstall-all.valid: $(chapter_uninstall_all_SOURCES) $(chapter_uninstall_all_IDMAPS)
+chapter-uninstall-all.validwarn: $(chapter_uninstall_all_SOURCES) $(chapter_uninstall_all_IDMAPS)
+chapter-uninstall-all-prepped.xml: $(chapter_uninstall_all_SOURCES) $(chapter_uninstall_all_IDMAPS)
+chapter-uninstall-all-manprepped.xml: $(chapter_uninstall_all_SOURCES) $(chapter_uninstall_all_IDMAPS)
+chapter-uninstall-all-remprepped.xml: $(chapter_uninstall_all_SOURCES) $(chapter_uninstall_all_IDMAPS)
+
+chapter_upgrade_all_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+chapter_upgrade_all_IMAGES =
+chapter_upgrade_all_SOURCES = chapter-upgrade-all.xml $(chapter_upgrade_all_INCLUDES)
+chapter_upgrade_all_IDMAPS = \
+ metadata/installation-all.idmap
+chapter-upgrade-all.validpure: $(chapter_upgrade_all_SOURCES)
+chapter-upgrade-all.titles: $(chapter_upgrade_all_SOURCES)
+chapter-upgrade-all.useless: $(chapter_upgrade_all_SOURCES)
+chapter-upgrade-all.valid: $(chapter_upgrade_all_SOURCES) $(chapter_upgrade_all_IDMAPS)
+chapter-upgrade-all.validwarn: $(chapter_upgrade_all_SOURCES) $(chapter_upgrade_all_IDMAPS)
+chapter-upgrade-all-prepped.xml: $(chapter_upgrade_all_SOURCES) $(chapter_upgrade_all_IDMAPS)
+chapter-upgrade-all-manprepped.xml: $(chapter_upgrade_all_SOURCES) $(chapter_upgrade_all_IDMAPS)
+chapter-upgrade-all-remprepped.xml: $(chapter_upgrade_all_SOURCES) $(chapter_upgrade_all_IDMAPS)
+
+installation_all_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+installation_all_IMAGES =
+installation_all_SOURCES = installation-all.xml $(installation_all_INCLUDES)
+installation_all_IDMAPS = \
+ ../refman-common/metadata/bug-reports.idmap \
+ metadata/chapter-upgrade-all.idmap \
+ metadata/installation-all.idmap
+installation-all.validpure: $(installation_all_SOURCES)
+installation-all.titles: $(installation_all_SOURCES)
+installation-all.useless: $(installation_all_SOURCES)
+installation-all.valid: $(installation_all_SOURCES) $(installation_all_IDMAPS)
+installation-all.validwarn: $(installation_all_SOURCES) $(installation_all_IDMAPS)
+installation-all-prepped.xml: $(installation_all_SOURCES) $(installation_all_IDMAPS)
+installation-all-manprepped.xml: $(installation_all_SOURCES) $(installation_all_IDMAPS)
+installation-all-remprepped.xml: $(installation_all_SOURCES) $(installation_all_IDMAPS)
+
+mysql_enterprise_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+mysql_enterprise_IMAGES =
+mysql_enterprise_SOURCES = mysql-enterprise.xml $(mysql_enterprise_INCLUDES)
+mysql_enterprise_IDMAPS =
+mysql-enterprise.validpure: $(mysql_enterprise_SOURCES)
+mysql-enterprise.titles: $(mysql_enterprise_SOURCES)
+mysql-enterprise.useless: $(mysql_enterprise_SOURCES)
+mysql-enterprise.valid: $(mysql_enterprise_SOURCES) $(mysql_enterprise_IDMAPS)
+mysql-enterprise.validwarn: $(mysql_enterprise_SOURCES) $(mysql_enterprise_IDMAPS)
+mysql-enterprise-prepped.xml: $(mysql_enterprise_SOURCES) $(mysql_enterprise_IDMAPS)
+mysql-enterprise-manprepped.xml: $(mysql_enterprise_SOURCES) $(mysql_enterprise_IDMAPS)
+mysql-enterprise-remprepped.xml: $(mysql_enterprise_SOURCES) $(mysql_enterprise_IDMAPS)
+
+starting_all_INCLUDES = \
+ ../common/fixedchars.ent \
+ ../gui-common/gui-common.ent \
+ ../refman-common/urls.ent \
+ all-entities.ent
+starting_all_IMAGES =
+starting_all_SOURCES = starting-all.xml $(starting_all_INCLUDES)
+starting_all_IDMAPS =
+starting-all.validpure: $(starting_all_SOURCES)
+starting-all.titles: $(starting_all_SOURCES)
+starting-all.useless: $(starting_all_SOURCES)
+starting-all.valid: $(starting_all_SOURCES) $(starting_all_IDMAPS)
+starting-all.validwarn: $(starting_all_SOURCES) $(starting_all_IDMAPS)
+starting-all-prepped.xml: $(starting_all_SOURCES) $(starting_all_IDMAPS)
+starting-all-manprepped.xml: $(starting_all_SOURCES) $(starting_all_IDMAPS)
+starting-all-remprepped.xml: $(starting_all_SOURCES) $(starting_all_IDMAPS)
+
Added: trunk/th/gui-common/all-entities.ent
===================================================================
--- trunk/th/gui-common/all-entities.ent (rev 0)
+++ trunk/th/gui-common/all-entities.ent 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 769 bytes
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+ This file names all the entity files needed by .xml files in the
+ current directory. All ENTITY declarations should be given
+ first, followed by references to the those entities.
+-->
+<!ENTITY % fixedchars.entities SYSTEM "../common/fixedchars.ent">
+<!ENTITY % urls.entities SYSTEM "../refman-common/urls.ent">
+<!ENTITY % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+%fixedchars.entities;
+%urls.entities;
+%gui-common.entities;
+
Added: trunk/th/gui-common/appendix-common-files.xml
===================================================================
--- trunk/th/gui-common/appendix-common-files.xml (rev 0)
+++ trunk/th/gui-common/appendix-common-files.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 42, Lines Deleted: 0; 1536 bytes
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" >
+<appendix id="mysql-gui-appendix-xml-files">
+
+ <title>XML Files Common to the MySQL GUI Applications</title>
+
+ <para>
+ On Windows, XML files common to all MySQL GUI applications are
+ stored in the <literal>C:\Documents and
+ Settings\<replaceable>UserName</replaceable>\Application
+ Data\MySQL</literal> directory, where
+ <replaceable>UserName</replaceable> is the name of the current
+ Windows user. On Linux, the files are stored in the
+ <literal>~/.mysqlgui</literal> directory.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>mysqlx_common_options.xml</literal>: Stores options
+ selected in the <link
+linkend="mysql-gui-options">Options
+ dialog</link>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>mysqlx_user_connections.xml</literal>: This file is
+ described in
+ <link
+ linkend="mysql-gui-appendix-store-connections">How
+ Connections are Stored</link>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+</appendix>
+<!-- END COMMON XML FILES -->
Added: trunk/th/gui-common/appendix-connection-storage.xml
===================================================================
--- trunk/th/gui-common/appendix-connection-storage.xml (rev 0)
+++ trunk/th/gui-common/appendix-connection-storage.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 0; 2712 bytes
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" >
+<appendix id="mysql-gui-appendix-store-connections">
+
+ <title>How Connections Are Stored</title>
+
+ <para>
+ On Windows, connection profiles are stored in <literal>C:\Documents
+ and Settings\<replaceable>UserName</replaceable>\Application
+ Data\MySQL</literal> directory, where
+ <replaceable>UserName</replaceable> is the name of the current
+ Windows user. On Linux, the files are stored in the
+ <literal>~/.mysqlgui</literal> directory. The settings are stored in
+ a file called <literal>mysqlx_user_connections.xml</literal>. The
+ contents of that file look like this:
+ </para>
+
+<programlisting>
+<?xml version="1.0"?>
+ <user_connections>
+ <last_connection>1</last_connection>
+ <password_storage_type>2</password_storage_type>
+ <user_connection>
+ <connection_name></connection_name>
+ <username>root</username>
+ <hostname>localhost</hostname>
+ <port>3306</port>
+ <schema></schema>
+ <advanced_options/>
+ <storage_path></storage_path>
+ <notes></notes>
+ <connection_type>0</connection_type>
+ <storage_type>2</storage_type>
+ <password></password>
+ </user_connection>
+ ...
+</programlisting>
+
+ <para>
+ You can edit the file manually, but take care not to invalidate the
+ XML. When applying changes by editing and saving the file, those
+ changes will show up the next time you open the
+ <link
+
+linkend="mysql-gui-options-connections">Connections</link>
+ section of the <link
+ linkend="mysql-gui-options">Options
+ Dialog</link>. You do not need to restart your application for the
+ changes to take effect.
+ </para>
+
+ <para>
+ Database administrators may want to edit the file and then copy it
+ to another machine running the MySQL GUI tools. This makes it easy
+ to have identical connection profiles on a number of machines,
+ without having to set up those profiles individually. All XML
+ configuration files for the MySQL GUI Tools are cross-platform
+ compatible and can be transferred between Windows and Linux
+ machines.
+ </para>
+
+</appendix>
+<!-- END CONNECTION STORAGE -->
Added: trunk/th/gui-common/appendix-source-install.xml
===================================================================
--- trunk/th/gui-common/appendix-source-install.xml (rev 0)
+++ trunk/th/gui-common/appendix-source-install.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 812, Lines Deleted: 0; 22005 bytes
@@ -0,0 +1,812 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<appendix id="mysql-gui-install-source">
+
+ <title>Installing From Source</title>
+
+ <section id="mysql-gui-install-source-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ Normally, you will want to install the MySQL GUI tools from
+ binaries. We put a lot of effort into making sure that our
+ binaries are built with the best possible options. If, for
+ whatever reason, you wish to compile the tools yourself, follow
+ these instructions.
+ </para>
+
+ </section>
+
+<!-- END INTRODUCTION -->
+
+ <section id="mysql-gui-install-source-download">
+
+ <title>Downloading The Source Code</title>
+
+ <para>
+ The source code for the MySQL GUI tools is available from our
+ public Subversion trees at
+ <ulink url="http://dev.mysql.com/tech-resources/sources.html"/>.
+ </para>
+
+ <para>
+ You will need the <literal>mysql-gui-common</literal> tree
+ regardless of which GUI tools you intend to build. The
+ <literal>mysql-gui-common</literal> tree contains source and
+ graphics files used for all MySQL GUI tools.
+ </para>
+
+ <para>
+ To be able to access these trees, you must have Subversion
+ installed. Subversion is freely available from
+ <ulink url="http://subversion.tigris.org/"/>.
+ </para>
+
+ </section>
+
+<!-- END GET SOURCE -->
+
+ <section id="mysql-gui-install-source-windows">
+
+ <title>Building from Source under Windows</title>
+
+ <para>
+ Installing from source under Windows requires multiple commercial
+ compilers and because of this it is preferable to install from
+ binaries. If you meet the prerequisites needed you can build the
+ MySQL GUI tools from source under Windows.
+ </para>
+
+ <section
+id="mysql-gui-install-source-windows-prerequisites">
+
+ <title>Prerequisites</title>
+
+ <para>
+ To compile the MySQL GUI tools from source under Windows, you
+ need Borland Delphi 7, Microsoft Visual Studio.NET 2003, and
+ some libraries which are available on the internet as open
+ source software. Make sure the programs
+ <literal>DCC32.exe</literal> and <literal>DEVENV.exe
+ /?</literal> can be launched from the command line.
+ </para>
+
+ <para>
+ You will need the following libraries to build from source:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ glib-2.0
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ libxml-2
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ mysql client libraries (4.0 or newer, 5.0 preferred)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ pcre-1.4
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MS Visual C runtime libraries 7.1
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Java include files 1.4.2_04
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Lua 5.0.2
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+<!-- Prerequisites -->
+
+ <section id="mysql-gui-install-source-windows-compiling">
+
+ <title>Compiling and Building</title>
+
+ <para>
+ Make sure you have cloned the
+ <literal>mysql-administrator</literal>,
+ <literal>mysql-gui-common</literal>, and
+ <literal>mysql-query-browser</literal> trees, and that their
+ local directories are located in the same directory, for example
+ in <literal>Personal Files\MySQLGUI\</literal>.
+ </para>
+
+ <para>
+ The source files and libraries should be placed into the
+ following tree structure:
+ </para>
+
+<programlisting>
+ Working Directory
+ |
+ |- mysql-administrator
+ |- mysql-gui-common
+ |- mysql-query-browser
+ |- mysql-gui-win-res
+ |
+ |-include
+ | |
+ | |-glib-2.0
+ | |-java
+ | | |
+ | | |-win32
+ | |
+ | |-libxml
+ | |-lua
+ | |-mysql
+ | |-pcre
+ | |-windows
+ |
+ |-lib
+ |
+ |-glib-2.0
+ |-java
+ |-libxml
+ |-lua
+ |-mysql
+ |-pcre
+ |-windows
+</programlisting>
+
+ <section id="mysql-gui-install-source-windows-compiling-command-line">
+
+ <title>Building from Command Line</title>
+
+ <para>
+ To build from the command line open a windows command line
+ prompt and change into the main repository of the tool (i.e.
+ for &administrator; this is
+ <literal>work\mysql-administrator</literal>). There are three
+ batch-files to start the build:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ build_debug.cmd
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ build_release.cmd
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ build_commercial.cmd
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Execute one of those to generate a runtime image of the
+ application. It will be generated in a
+ <literal>bin\windows</literal> directory.
+ </para>
+
+ <para>
+ Another method is to doubleclick on one of the
+ <literal>build_<replaceable>buildtype</replaceable>.cmd</literal>
+ files, where <replaceable>buildtype</replaceable> is one of
+ <literal>debug</literal>, <literal>release</literal>, and
+ <literal>commercial</literal>. The
+ <literal>commercial</literal> build script is for users with
+ commercial licenses, and makes use of the commercial version
+ of the MySQL client library.
+ </para>
+
+ </section>
+
+<!-- END COMMAND LINE -->
+
+ <section id="mysql-gui-install-source-windows-compiling-ide">
+
+ <title>Building from the IDE</title>
+
+ <para>
+ Before you can open any projects, you have to install these
+ components. Otherwise some of the forms will not open and you
+ will receive error messages.
+ </para>
+
+ <para>
+ To install the components, goto the
+ <literal>mysql-gui-common\source\windows\</literal> directory.
+ Copy the following directories to your Delphi source directory
+ (<literal>C:\Program Files\Borland\Delphi7\Source\</literal>).
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ png
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SynEdit
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ TNT
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ UniCodeEditor
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ VirtualTreeview
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Then doubleclick each <literal>*.dpk</literal> file outlined
+ below. It will open Delphi. Press compile and install to
+ install the components. Repeat this for each
+ <literal>*.dpk</literal> file.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ SynEdit\Packages\SynEdit_D7.dpk
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ TNT\Packages\TntUnicodeVcl_D70.dpk
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ VirtualTreeview\Packages\VirtualTreesD7D.dpk
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ UniCodeEditor\Packages\UniCodeEditorD7.dpk
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ These components have to be installed via the
+ <guimenu>Install</guimenu> option of the
+ <guimenu>Component</guimenu> menu. Click on the
+ <guibutton>Browse</guibutton> button and select the files
+ below. Press <guibutton>OK</guibutton> after each file.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ png\PNGImage.pas
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ After installing the components you can open the projects as
+ outlined below.
+ </para>
+
+ <para>
+ To build the application from the Delphi 7 IDE simply
+ doubleclick the
+ <literal>edit_<replaceable>xxxx</replaceable>.cmd</literal>.
+ This will launch Delphi 7 and open the file. To generate the
+ complete runtime image select <guimenu>Build All
+ Projects</guimenu> option from the <guimenu>Project</guimenu>
+ menu.
+ </para>
+
+ <para>
+ Like for building from command line there are three different
+ files.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ edit_debug.cmd
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ edit_release.cmd
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ edit_commercial.cmd
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The runtime image will be generated in a
+ <literal>bin\windows</literal> directory.
+ </para>
+
+ <para>
+ <emphasis>Opening the Delphi project not using the
+ <literal>edit_*.cmd</literal> script will lead to incorrect
+ project settings and problems while building the
+ projects.</emphasis>
+ </para>
+
+ </section>
+
+<!-- END BUILDING IDE -->
+
+ </section>
+
+<!-- COMPILING AND BUILDING -->
+
+ </section>
+
+<!-- BUILDING FROM SOURCE UNDER WINDOWS -->
+
+ <section id="mysql-gui-install-source-linux">
+
+ <title>Building from Source under Linux</title>
+
+ <section
+id="mysql-gui-install-source-linux-prerequisites">
+
+ <title>Prerequisites</title>
+
+ <para>
+ The easiest way to install required packages is by using an
+ automatic dependency resolving package manager, such as
+ <literal>apt-get</literal> or <literal>yum</literal>. You can
+ install these dependencies by hand, but it will be a very
+ tedious process since some of them require other packages that
+ require other packages and so on.
+ </para>
+
+ <para>
+ Common requirements are listed below. For some distributions the
+ package name is also mentioned.
+ </para>
+
+ <table>
+ <title>Required Components</title>
+ <tgroup cols="4">
+ <colspec colwidth="1.5in"/>
+ <colspec colwidth="1in"/>
+ <colspec colwidth="1in"/>
+ <colspec colwidth="1in"/>
+ <thead>
+ <row>
+ <entry><emphasis role="bold">Software</emphasis></entry>
+ <entry><emphasis role="bold">Version</emphasis></entry>
+ <entry><emphasis role="bold">Ubuntu 6</emphasis></entry>
+ <entry><emphasis role="bold">SuSE 10.x</emphasis></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>gcc/g++</entry>
+ <entry>4</entry>
+ <entry>g++</entry>
+ <entry>gcc-c++</entry>
+ </row>
+ <row>
+ <entry>autoconf, automake libtool</entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>x11-libs</entry>
+ <entry></entry>
+ <entry>libx11-dev</entry>
+ <entry>xorg-x11-devel</entry>
+ </row>
+ <row>
+ <entry>glibc</entry>
+ <entry></entry>
+ <entry>libc6-dev</entry>
+ <entry>xorg-xll-devel</entry>
+ </row>
+ <row>
+ <entry>libstdc++</entry>
+ <entry></entry>
+ <entry>libstdc++6-4.0-dev</entry>
+ <entry>libstdc++devel</entry>
+ </row>
+ <row>
+ <entry>glib</entry>
+ <entry>2.6+</entry>
+ <entry>libglib2.0-dev</entry>
+ <entry>glib2-devel</entry>
+ </row>
+ <row>
+ <entry>gtk+</entry>
+ <entry>2.6+</entry>
+ <entry>libgtk2.0-dev</entry>
+ <entry>gtk2-devel</entry>
+ </row>
+ <row>
+ <entry>libglade2</entry>
+ <entry>2.5+</entry>
+ <entry>libglade2-dev</entry>
+ <entry>libglade2-devel</entry>
+ </row>
+ <row>
+ <entry>libsigc++</entry>
+ <entry>2.0.x</entry>
+ <entry>libsigc++-2.0-dev</entry>
+ <entry>libsigc++2-devel</entry>
+ </row>
+ <row>
+ <entry>glibmm-2.4</entry>
+ <entry>2.4</entry>
+ <entry>libglibmm-2.4-dev</entry>
+ <entry>glibmm24-devel</entry>
+ </row>
+ <row>
+ <entry>gtkmm-2.4</entry>
+ <entry>2.4</entry>
+ <entry>libgtkmm-2.4-dev</entry>
+ <entry>gtkmm24-devel</entry>
+ </row>
+ <row>
+ <entry>pcre</entry>
+ <entry>4.x or newer</entry>
+ <entry>libpcre3-dev</entry>
+ <entry>pcre-devel</entry>
+ </row>
+ <row>
+ <entry>pkgconfig</entry>
+ <entry>0.15+</entry>
+ <entry>pkg-config</entry>
+ <entry>pkgconfig</entry>
+ </row>
+ <row>
+ <entry>libxml2</entry>
+ <entry>2.6.x</entry>
+ <entry>libxml2-dev</entry>
+ <entry>libxml2-devel</entry>
+ </row>
+ <row>
+ <entry>MySQL 5.0 or 5.1 client libs and headers</entry>
+ <entry></entry>
+ <entry>libmysqlclient15-dev</entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ Additional requirements for building &query_browser; are:
+ </para>
+
+ <table>
+ <title>Requirements for &query_browser;</title>
+ <tgroup cols="4">
+ <colspec colwidth="1.5in"/>
+ <colspec colwidth="1in"/>
+ <colspec colwidth="1in"/>
+ <colspec colwidth="1in"/>
+ <thead>
+ <row>
+ <entry><emphasis role="bold">Software</emphasis></entry>
+ <entry><emphasis role="bold">Version</emphasis></entry>
+ <entry><emphasis role="bold">Ubuntu 6</emphasis></entry>
+ <entry><emphasis role="bold">SuSE 10.x</emphasis></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>libgtkhtml</entry>
+ <entry>2.11 or 3.x</entry>
+ <entry>libgtkhtml2-dev</entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>libgnomeprint</entry>
+ <entry>2.2</entry>
+ <entry>libgnomeprint2.2-dev</entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+
+ </section>
+
+<!-- Prerequisites -->
+
+ <section id="mysql-gui-install-source-linux-compiling">
+
+ <title>Compiling and Building</title>
+
+ <para>
+ To build any of the tools, you need to have the source tree for
+ <literal>mysql-gui-common</literal> and the tree for the desired
+ app (i.e.: <literal>mysql-administrator</literal>,
+ <literal>mysql-query-browser</literal>) in the same top-level
+ directory.
+ </para>
+
+ <para>
+ First build <literal>mysql-gui-common</literal>:
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ cd mysql-gui-common
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ sh ./autogen.sh
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ ./configure
+ --prefix=/opt/mysql-<replaceable>administrator</replaceable>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ make
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ make install
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ The <literal>--prefix</literal> option can have whatever value you
+ want, normally one would specify <literal>/usr/local</literal>
+ (the default) or <literal>/usr</literal>, but for making
+ precompiled binaries, something in <literal>/opt</literal> might
+ be more appropriate.
+ </para>
+
+ <para>
+ After you have successfully built
+ <literal>mysql-gui-common</literal>, you can build the individual
+ tools (in this example we will build mysql-administrator):
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ cd mysql-administrator
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ sh ./autogen.sh
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ ./configure
+ --prefix=/opt/mysql-<replaceable>administrator</replaceable>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ make
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ make install
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ If everything went well, things should be properly built and
+ installed.
+ </para>
+
+ <section id="mysql-gui-install-source-linux-compiling-static">
+
+ <title>Building Static Binaries</title>
+
+ <para>
+ Building static binaries is non-trivial under Linux, due to the
+ enormous number of library dependencies that come from GNOME and
+ associated libraries. Additionally:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Many libraries do not come with their static (lib*.a)
+ versions shipped, so we need to build them ourselves.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some libraries can't be linked statically, such as glibc,
+ because of libnss*.so.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some libraries depend on data files and modules from the
+ original package, especially in the case of gtk/gnome.
+ Problems don't only appear when the user is missing these
+ data files; things may not work because different
+ distributions put files in different paths.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The current solution is to build a partially static binary, with
+ the most common libraries left dynamically linked
+ (<literal>glibc</literal> and <literal>gtk</literal>).
+ <literal>gtkmm</literal>, <literal>gtksourceview</literal>,
+ <literal>gtkhtml</literal> and dependencies (like gnome) are
+ linked statically. The ideal solution would be to build custom
+ binaries for each major/chosen distribution, but we don't have
+ time/resources for that at the moment.
+ </para>
+
+ <para>
+ To build these binaries:
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Look at the <literal>source/linux/static_make</literal>
+ script for all the files that should be removed/moved out of
+ <literal>/usr/lib</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Run the script.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ That's needed to force the linker to look for the static version
+ of each library and also to explicitly list the dependency libs
+ that were otherwise linked to the dynamic libs.
+ </para>
+
+ </section>
+
+<!-- END BUILDING STATIC -->
+
+ <section id="mysql-gui-install-source-linux-compiling-rpm">
+
+ <title>Building RPMs</title>
+
+ <para>
+ For building RPMs, a spec file is already supplied and will be
+ made automatically after <literal>./configure</literal> is ran.
+ The spec file expects a source tarball with the following
+ structure:
+ </para>
+
+<programlisting>mysql-administrator/ mysql-administrator/mysql-gui-common/* »
+mysql-administrator/mysql-administrator/*</programlisting>
+
+ <para>
+ The contents of each subdirectory is the entire source tree for
+ each tool (Windows specific files and source metadata are
+ optional, of course). You must make a <literal>tar.gz</literal>
+ file and put it in <literal>/usr/src/redhat/SOURCES</literal>
+ (or whatever is your rpm SOURCES directory).
+ </para>
+
+ <para>
+ Then, execute: <literal>rpmbuild -ba
+ mysql-administrator.spec</literal>
+ </para>
+
+ <para>
+ That should build the srpm and rpm files for the tool.
+ </para>
+
+ </section>
+
+<!-- END COMPILING RPMS -->
+
+ </section>
+
+<!-- Compiling and Building -->
+
+<!-- Building from Source under Linux -->
+
+</appendix>
+<!-- END SOURCE INSTALL -->
Added: trunk/th/gui-common/appendix-third-party.xml
===================================================================
--- trunk/th/gui-common/appendix-third-party.xml (rev 0)
+++ trunk/th/gui-common/appendix-third-party.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 49, Lines Deleted: 0; 1792 bytes
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" >
+<appendix id="mysql-gui-appendix-third-party-software">
+
+ <title>Third-party Software Used by the MySQL GUI Tools</title>
+
+ <para>
+ The MySQL GUI tools incorporate PCRE and PNG support through the use
+ of third-party libraries.
+ </para>
+
+ <section id="mysql-gui-appendix-third-party-software-pcre">
+
+ <title>PCRE Library</title>
+
+ <para>
+ Regular expression support is provided by the PCRE library
+ package, which is open source software, written by Philip Hazel,
+ and copyright by the University of Cambridge, England. The source
+ for the PCRE library can be found at:
+ <ulink
+
+url="ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/">ftp:/
+ /ftp.csx.cam.ac.uk/pub/software/programming/pcre/</ulink>.
+ </para>
+
+ </section>
+
+<!-- PCRE LIBRARY -->
+
+ <section id="mysql-gui-appendix-third-party-software-png">
+
+ <title>PNG Support</title>
+
+ <para>
+ PNG support for the Windows version is provided by the TPNGImage
+ component which is open source software, written and copyright by
+ Gustavo Daud. The source for the TPNGImage can be found at:
+ <ulink url="http://pngdelphi.sourceforge.net">
+ http://pngdelphi.sourceforge.net </ulink>.
+ </para>
+
+ </section>
+
+<!-- PNG SUPPORT -->
+
+</appendix>
+<!-- THIRD-PARTY SOFTWARE USED BY GUI TOOLS -->
Added: trunk/th/gui-common/appendix-translator-notes.xml
===================================================================
--- trunk/th/gui-common/appendix-translator-notes.xml (rev 0)
+++ trunk/th/gui-common/appendix-translator-notes.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 86, Lines Deleted: 0; 2669 bytes
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" >
+<appendix id="mysql-gui-appendix-notes-for-translators">
+
+ <title>Notes for Translators</title>
+
+ <para>
+ You may find that the MySQL GUI tools and/or their documentation are
+ not available in your preferred language. If you would like to
+ translate the software, or its documentation, or participate in that
+ translation, <emphasis>please contact the MySQL documentation team
+ before starting your translation.</emphasis>
+ </para>
+
+ <para>
+ The MySQL documentation team's address is
+ <email>docs@stripped</email>. In your email, please state what you
+ would like to translate (the tools, their documentation, or even the
+ whole MySQL reference manual if you dare), and give some information
+ regarding your background:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ What is your name?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Where do you live?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ How long have you used MySQL?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Have you done other translations?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Will you work alone or with a group of translators?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ What's your timetable regarding the translation?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ What is your motivation for translating?
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ We will get back to you as soon as possible.
+ </para>
+
+ <para>
+ The format used for both software and documentation is
+ <emphasis role="bold">DocBook XML</emphasis>. From that base format,
+ all other available formats (HTML, CHM, PDF, etc.) are being
+ generated. It would be a pity if you started translating, say, the
+ HTML version of this documentation, because we will not be able to
+ use it in that format. Also, you might find that someone else has
+ already done (or is in the process of doing) that translation. So,
+ once again, please contact the MySQL documentation team first.
+ </para>
+
+</appendix>
+<!-- Notes for Translators -->
Added: trunk/th/gui-common/appendix-troubleshooting.xml
===================================================================
--- trunk/th/gui-common/appendix-troubleshooting.xml (rev 0)
+++ trunk/th/gui-common/appendix-troubleshooting.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 93, Lines Deleted: 0; 3457 bytes
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" >
+<appendix id="mysql-gui-appendix-troubleshooting">
+
+ <title>Troubleshooting Application Errors</title>
+
+ <para></para>
+
+ <section id="mysql-gui-appendix-troubleshooting-connection-errors">
+
+ <title>Troubleshooting Connection Errors</title>
+
+ <para>
+ If an error occurs when you select a connection profile and
+ attempt to establish a connection to the MySQL server named in the
+ profile, a window containing error information will be displayed
+ (see figure).
+ </para>
+
+ <figure>
+ <title>Error message dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/connectionerror.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Error message dialog</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ Normally, this means either that the credentials specified in the
+ profile are wrong (wrong username, wrong password), or that you do
+ not have privileges to connect to the MySQL server from the client
+ machine. See <xref linkend="access-denied"/>, for more
+ information.
+ </para>
+
+ <para>
+ However, another cause of connection failure is that there might
+ be a network problem that prevents you from reaching the machine
+ where the MySQL server is running. For this reason, the error
+ dialog provides a <guibutton>PING</guibutton> button. Clicking
+ this button will send an ICMP PING request to the MySQL server
+ host machine. If the host machine is available over the network,
+ you will see something like this:
+ </para>
+
+<programlisting>
+Reply from 127.0.0.1: Time=0ms TTL=128
+Reply from 127.0.0.1: Time=1ms TTL=128
+</programlisting>
+
+ <para>
+ This would indicate that the machine is reachable, and that the
+ cause of connection failure is not a network problem.
+ </para>
+
+ </section>
+
+<!-- TROUBLESHOOTING CONNECTION ERRORS -->
+
+ <section
+id="mysql-gui-appendix-troubleshooting-display-problems">
+
+ <title>Troubleshooting Display Problems</title>
+
+ <para>
+ If, under Windows, the controls in the windows look somehow
+ displaced, select <guimenu>Start</guimenu>, <guimenu>Control
+ Panel</guimenu>, <guimenu>Display</guimenu>. Select the
+ <guilabel>Settings</guilabel> tab and click the
+ <guibutton>Advanced...</guibutton> button. Change your DPI
+ settings to <literal>Normal (96 DPI)</literal>.
+ </para>
+
+ <para>
+ If, under Linux, messages and captions appear very big, your
+ display resolution is probably set too high. Use
+ <literal>gnome-font-properties</literal> to change your default
+ font to a smaller value or go to <literal>Details</literal> and
+ set your resolution to <literal>72</literal> or some other more
+ appropriate value.
+ </para>
+
+ </section>
+
+<!-- TROUBLESHOOTING DISPLAY PROBLEMS -->
+
+</appendix>
+<!-- END TROUBLESHOOTING APPENDIX -->
Added: trunk/th/gui-common/chapter-grt-shell.xml
===================================================================
--- trunk/th/gui-common/chapter-grt-shell.xml (rev 0)
+++ trunk/th/gui-common/chapter-grt-shell.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 733, Lines Deleted: 0; 25129 bytes
@@ -0,0 +1,733 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % fixedchars.entities SYSTEM "../common/fixedchars.ent">
+ %fixedchars.entities;
+ <!ENTITY % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+ %gui-common.entities;
+ ]>
+<chapter id="grt-shell">
+
+ <title>The Generic Runtime Environment (GRT) Shell</title>
+
+ <section id="grt-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The GRT is a thin C layer, inspired by Objective C, which allows
+ for dynamic typing and dynamic data objects. The GRT is used by
+ both &workbench; and the &migration_toolkit; and provides a means
+ for expanding these tools. Through the use of the GRT, these tools
+ can support new behavior and data sources using code written in
+ languages such as C, C++, Java, Python, and Lua with support for
+ Mono forthcoming.
+ </para>
+
+ <para>
+ The GRT is not only useful for expanding &gui_tools;. By using a
+ script file from within the GRT shell you can perform repetitive
+ tasks programmatically from the command line. Suppose, for
+ example, that you have multiple schemata that you wish to migrate
+ to MySQL. You can do this once using the graphical interface, in
+ the process saving the procedure as a script file. You can then
+ adapt this script file and run it unattended from the GRT shell.
+ </para>
+
+ <para>
+ The preferred development language is <literal>Lua</literal>, a
+ lightweight scripting language expressly designed for extending
+ applications. For more information about this language see
+ <ulink url="http://www.lua.org/">lua.org</ulink>.
+ </para>
+
+ <note>
+ <para>
+ The GRT shell is used both in the &migration_toolkit; and the
+ &workbench;. However, the &migration_toolkit; is only available
+ for Windows. The implementation of the GRT Shell varies
+ depending upon the operating system (OS).
+ </para>
+ </note>
+
+ </section>
+
+<!-- End INTRODUCTION -->
+
+ <section id="exploring-grt-shell">
+
+ <title>Exploring the GRT Shell</title>
+
+ <para>
+ To open the GRT shell from within the &migration_toolkit; choose
+ the <guimenu>GRT Environment Shell</guimenu> option under the
+ <guimenu>Tools</guimenu> menu. In &workbench; under Windows,
+ choose <guimenu>View</guimenu>, <guimenu>Advanced</guimenu>,
+ <guimenu>Show GRT Shell</guimenu>. Under Linux simply choose
+ <guimenu>View</guimenu> and then <guimenu>GRT Console</guimenu>
+ and with Mac OS X choose the <guimenu>Window</guimenu> menu and
+ then <guimenu>GRT Shell</guimenu>. However, the simplest way to
+ open the GRT Shell in either application or under any OS is to use
+ the <keycap>F4</keycap> key. If you haven't docked the GRT shell
+ window you should see something similar to the following:
+ </para>
+
+ <figure>
+ <title>The GRT shell (Windows)</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/published/grt-shell.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">The GRT shell (Windows)</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ The GRT shell itself is the default tab on the left of the screen.
+ Beside it is the <literal>Snippets</literal> tab, used for saving
+ code snippets.
+ </para>
+
+ <para>
+ On the right, is the <literal>GRT Globals
+ Tree</literal>—showing the various objects, variables,
+ structures, and code modules used by the application. These
+ objects are all directly accessible from the shell.
+ </para>
+
+ <section id="grt-menu-items">
+
+ <title>Menu Items</title>
+
+ <para>
+ The menu runs across the top of the screen and varies
+ significantly depending upon which OS you are using. Since the
+ &migration_toolkit; is currently only implemented on Windows,
+ all references to invoking the GRT shell from this application
+ apply only to the Windows OS.
+ </para>
+
+ <section id="grt-shell-menu">
+
+ <title>The File or Shell Menu</title>
+
+ <section id="grt-windows-shell-menu">
+
+ <title>Windows File Menu</title>
+
+ <para id="grt-file-menu">
+ Currently only two of the submenus under the
+ <guimenu>File</guimenu> menu are implemented;
+ <guimenu>Exit</guimenu>, which simply exits the GRT shell,
+ and <guimenu>Open Script</guimenu>. The <guimenu>Open
+ Script</guimenu> option is for opening existing
+ <literal>Lua</literal> scripts and is only implemented under
+ Windows.
+ </para>
+
+ <para>
+ Sample scripts are found in the <filename>Scripts</filename>
+ directory which is immediately below the installation
+ directory. Opening a script from this menu option will
+ create an additional tab labeled with the name of the
+ script. Click on this tab to see the file contents. You may
+ paste text between the <literal>GRT Shell</literal> tab and
+ any script tab.
+ </para>
+
+ </section>
+
+ <section id="grt-linux-shell-menu">
+
+ <title>Linux Shell Menu</title>
+
+ <para>
+ Under Linux the <guimenu>Shell</guimenu> menu shows menu
+ items for closing the shell, refreshing the objects listed
+ in the Global tree or saving the object tree.
+ </para>
+
+ <para>
+ The <guimenu>Save Tree ...</guimenu> menu option saves an
+ XML file of all the data types and classes shown in the
+ three tabs of the <literal>Objects Tree</literal>.
+ </para>
+
+ <para>
+ Under Linux there is no menu option to open a script.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="grt-view-menu">
+
+ <title>The View Menu</title>
+
+ <section id="grt-windows-view-menu">
+
+ <title>The View Menu: Windows</title>
+
+ <para>
+ The <guimenu>Refresh</guimenu> option of the
+ <guimenu>View</guimenu> menu refreshes the view of the
+ objects shown in the object tree tabs on the right.
+ </para>
+
+ <para>
+ The <guimenu>Display Type Info</guimenu> and
+ <guimenu>Display Object Values</guimenu> menu items toggle
+ the view of the objects in the <literal>Values</literal> tab
+ on the right. When checked, <guimenu>Display Type
+ Info</guimenu> shows the data type of objects and
+ <guimenu>Display Object Values</guimenu> shows their value.
+
+ <remark>
+ [PL]Same as panel below or not?
+ </remark>
+ </para>
+
+ <para>
+ The <guimenu>Display Object Refcount</guimenu> shows the
+ current number of references to specific objects.
+ </para>
+
+ </section>
+
+ <section id="grt-linux-view-menu">
+
+ <title>The View Menu: Linux</title>
+
+ <para>
+ The <guimenu>View</guimenu> menu has only one element,
+ <guimenu>Structure Only</guimenu> and it is not yet
+ activated.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="grt-osx-view-menu">
+
+ <title>Mac OS X Menu</title>
+
+ <para>
+ Under Mac OS X there are only two menu options,
+ <guimenu>Reload</guimenu> and <guimenu>Reload
+ Selected</guimenu>. <guimenu>Reload</guimenu> reloads all the
+ objects in the Object Tree panel and is equivalent to the
+ Windows <guimenu>View</guimenu>, <guimenu>Refresh</guimenu>
+ option. The <guimenu>Reload Selected</guimenu> option only
+ reloads the selected object.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="grt-shell-window">
+
+ <title>The Shell</title>
+
+ <para>
+ The GRT shell is principally used for running Lua scripts or
+ typing Lua commands directly. However, you can also access the
+ GRT Scripting Library functions and global functions and
+ objects. To see the available commands type
+ <quote><literal>?</literal></quote>.
+ </para>
+
+ <para>
+ Some OS-specific commands are also available. For instance,
+ under Windows you can clear the screen by typing
+ <command>cls</command>. Unlike most shells, you can cut and
+ paste text to and from the shell window.
+ </para>
+
+ <para>
+ Working from the command line is described in detail in
+ <xref linkend="using-grt-shell"/>.
+ </para>
+
+ <para>
+ The <literal>Snippets</literal> tab functions as a scratch pad
+ for saving code snippets. This makes it easy to reuse code and
+ does away with the need to retype it at the command line.
+ </para>
+
+ <para>
+ If you have opened script files as described in
+ <xref linkend="grt-file-menu"/>, there may be any number of tabs
+ to the right of the <literal>Snippets</literal> tab. These tabs
+ will be labeled with the names of the script files. As with the
+ <literal>Snippets</literal> tab you can cut and paste to or from
+ any of the tabs. This gives you the opportunity to test code
+ from the command line.
+ </para>
+
+ </section>
+
+ <section id="grt-globals-tree-panel">
+
+ <title>The Globals Tree Panel</title>
+
+ <para>
+ The <literal>Globals Tree</literal> is found on the right side
+ of the screen and is made up of three tabs,
+ <literal>Values</literal>, <literal>Structs</literal>, and
+ <literal>Modules</literal>.
+
+ <remark>
+ How are these different?
+ </remark>
+ </para>
+
+ <section id="grt-values-tab">
+
+ <title>The <literal>Values</literal> Tab</title>
+
+ <para>
+ The objects shown in this tab differ depending upon which
+ &gui_tools; application you are running. For example, if you
+ are running &workbench; you should find a
+ <literal>workbench</literal> object beneath the
+ <literal>root</literal> object. If you currently have a schema
+ loaded you should be able to find it beneath the
+ <literal>workbench</literal> object. Clicking
+ <literal>workbench </literal> will expose the
+ <literal>catalog</literal> object and clicking this object in
+ turn will show <literal>charcterSets</literal>,
+ <literal>schemata</literal>, and
+ <literal>simpleDataTypes</literal>. Beneath
+ <literal>schemata</literal> you should see the default
+ <literal>New Schema</literal> plus any schemata you have
+ loaded. Detailed information about the currently selected
+ object appears in the window below the module tree.
+ </para>
+
+ <para>
+ If you are running &migration_toolkit;, the
+ <literal>workbench</literal> object is absent but you will
+ find a <literal>migration</literal> object beneath the
+ <literal>root</literal> object. Both applications show the
+ <literal>rdbmsMgmt</literal> object.
+ </para>
+
+ <para>
+ When the <literal>Values</literal> tab is selected right
+ clicking an object in the Globals Tree panel opens a pop-up
+ menu with the options:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Refresh
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Remove Object
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Display Type Info
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Display Object Values
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Display Object RefCount
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ With the exception of <guimenu>Remove Object</guimenu>, these
+ options are the same as those shown in
+ <xref linkend="grt-view-menu"/>. You may remove any object
+ except the <literal>root</literal> object.
+ </para>
+
+ <note>
+ <para>
+ Note this pop-up menu only shows under Windows.
+ </para>
+ </note>
+
+ </section>
+
+ <section id="grt-struct-tab">
+
+ <title>The <literal>Struct</literal> Tab</title>
+
+ <para>
+ A <literal>struct</literal> is a user-defined data type formed
+ by combining primitive data types. This tab shows the
+ definitions of the structs used by the objects in the
+ <literal>Values</literal> tab and the modules in the
+ <literal>Modules</literal> tab.
+ </para>
+
+ <para>
+ When the <literal>Structs</literal> tab is selected right
+ clicking a structure in the list opens a pop-up menu with the
+ options:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Order by Name
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Order by Hierarchy
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Order by Package
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ <note>
+ <para>
+ Note this pop-up menu only shows under Windows.
+ </para>
+ </note>
+
+ <para>
+ The default view for this tab is by package, a grouping of
+ elements by functionality. Double-click a package to show
+ related structures. Under <literal>db.mgmt</literal>, for
+ example, you should see elements you are already familiar with
+ from the user interface, <literal>Connection</literal>,
+ <literal>Driver</literal>, and so forth. If an element can be
+ further decomposed, an arrow will show on it's left.
+ Double-click the item to reveal its constituent elements.
+ </para>
+
+ <para>
+ If you switch to the hierarchical view you'll find the
+ <literal>db.mgmt.driver</literal> object under the
+ <literal>GRT Object</literal> since this is the parent object
+ from which it is derived.
+ </para>
+
+ <para>
+ Ordering by name simply shows all the different objects
+ arranged alphabetically.
+ </para>
+
+ </section>
+
+ <section id="grt-modules-tab">
+
+ <title>The <literal>Modules</literal> Tab</title>
+
+ <para>
+ A module can be either a Python or Lua script or a Java class
+ file. Information about modules appears in the window below
+ the module tree. For example, go to the
+ <literal>Modules</literal> tab and click on the
+ <literal>ReverseEngineeringGeneric</literal> module. Double
+ click a module and you will see its methods.
+ </para>
+
+ <para>
+ Double clicking a method name will copy it into the GRT shell
+ window. You will see how useful this can be in
+ <xref linkend="using-grt-shell"/>.
+ </para>
+
+ </section>
+
+ </section>
+
+ </section>
+
+<!--End Exploring-->
+
+ <section id="using-grt-shell">
+
+ <title>Using the GRT Shell</title>
+
+ <para>
+ There are three built-in Lua modules that assist working from the
+ GRT shell:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>grtV</literal> – for accessing any
+ object/variable in the <literal>Values</literal> tab
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>grtS</literal> – for viewing the structs
+ defined in the <literal>Structures</literal> tab
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>grtM</literal> – for accessing any object in
+ the <literal>Modules</literal> tab
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ <para>
+ All items in all the tabs are accessible from the GRT shell.
+
+ <remark>
+ You can use the structs defined ...
+ </remark>
+ </para>
+
+ <para>
+ The script example below uses the <literal>getGlobal</literal>
+ method of the <literal>grtV</literal> object to return a list of
+ databases and then iterates through this list.
+ </para>
+
+<programlisting>
+dbs = grtV.getGlobal("/rdbmsMgmt/rdbms")
+for i = 1, grtV.getn(dbs) do
+ print(dbs[i].name)
+end
+</programlisting>
+
+ <para>
+ The <literal>getGlobal</literal> method returns the object found
+ at the path parameter passed to it. In this case, the object is a
+ list that is traversed using a <literal>for</literal> loop
+ controlled by the <literal>getn</literal> method which returns the
+ number of elements in the database list.
+ </para>
+
+ <para>
+ Running this <literal>for</literal> loop outputs the names of the
+ database formats supported by the &workbench; and the
+ &migration_toolkit;:
+ </para>
+
+<programlisting>
+"Oracle"
+"Mysql"
+"MaxDB"
+"GenericJdbc"
+"Mssql"
+"Access"
+</programlisting>
+
+ <para>
+ To discover all the methods available for a specific object, type
+ the object name preceded by a <quote><literal>?</literal></quote>.
+ For example typing <command>?grtV</command> shows:
+ </para>
+
+<programlisting>
+GRT Value Management Library - grtV
+-----------------------------------
+A library that contains functions to work with GRT values.
+
+clearList child diffMake
+diffApply duplicate fromXml
+getContentType getKey getListItemByObjName
+getListRefValueByObjName getn getGlobal
+insert load lookupAdd
+lookupId newDict newList
+newObj remove save
+setContentType setGlobal toLua
+toXml typeOf
+
+Type 'help grtV.<command>' to get help on a specific command.
+</programlisting>
+
+ <para>
+ <remark>
+ Add an object that will appear in the tab? i.e definition of an
+ different database struct?
+ </remark>
+ </para>
+
+ </section>
+
+ <section id="invoking-grt-from-command-line">
+
+ <title>Invoking the GRT Shell From the Command Line</title>
+
+ <note>
+ <para>
+ This capability is currently only available under Windows.
+ </para>
+ </note>
+
+ <para>
+ In addition to using the GRT shell from within the &workbench; or
+ the &migration_toolkit;, you can invoke it directly from the
+ command line. If the location of the &gui_tools; is not included
+ in the <literal>PATH</literal> variable, navigate to the
+ installation directory and find the <filename>grtsh.exe</filename>
+ file.
+ </para>
+
+ <para>
+ Execute this file by typing:
+ </para>
+
+<programlisting>
+C:\> <userinput>grtsh -?</userinput>
+</programlisting>
+
+ <para>
+ Do this and you should see the following listing:
+ </para>
+
+<programlisting>
+Usage: C:\Program Files\MySQL\MySQL Tools for 5.0\grtsh.exe [-classpath path] »
+ [-modulepath path] [-jvm library] [-d path] [-listen port] [-verbose] [-x] [luafile]
+ C:\Program Files\MySQL\MySQL Tools for 5.0\grtsh.exe -j structsfile outputdir
+ C:\Program Files\MySQL\MySQL Tools for 5.0\grtsh.exe -p structsfile outputdir
+
+ -lua ......... Use the Lua shell (default).
+ -py .......... Use the Python shell.
+ -classpath ... Sets the java classpath to the given value.
+ -modulepath .. Sets the location of the GRT module directory.
+ -jvm ......... The java virtual machine library to use (with absolute path).
+ -basedir ..... Path to the data files location.
+ -d path ...... Modules directory
+ -x ........... Exits the shell after running the specified file
+ luafile ...... File that is run at startup.
+
+ -listen port . Runs in 'remote agent' mode on the given port number.
+ -verbose ..... Prints detailed startup information.
+ -j ........... Generates Java classes from the given structs file.
+ -p ........... Generates PHP classes from the given structs file.
+ -D var=value . Sets a global shell variable to the given value.
+Environment variables:
+GRT_MODULE_PATH Equivalent to -modulepath, must point to the directory
+ where the grtsh binary resides
+</programlisting>
+
+ <para>
+ The default shell is the <literal>Lua</literal> shell and is
+ indicated by the <literal>/ ></literal> prompt. Using the
+ <option>-py</option> option opens a Python shell, indicated by the
+ <literal>/>>></literal> prompt.
+ </para>
+
+ <para>
+ If you wish to set the classpath for Java classes use the
+ <option>classpath</option> option. You may also change the Java
+ Virtual Machine (JVM) by using the <option>jvm</option> option
+ with the absolute path to the JVM you wish to use.
+ </para>
+
+ <para>
+ The <option>modulepath</option> option sets the location of the
+ <filename>dll</filename> files used with the GRT shell. These
+ files are located in the same directory as the
+ <filename>grtsh.exe</filename> file. You can also set this
+ directory by defining the environment variable,
+ <literal>GRT_MODULE_PATH</literal>.
+ </para>
+
+ <para>
+ The location of any data files you wish to use may be set using
+ the <option>basedir</option> option.
+
+ <remark>
+ [PL]What are data files?
+ </remark>
+ </para>
+
+ <para>
+ To see the various modules that are loaded at startup use the
+ <option>verbose</option> option. The java modules are stored in
+ the <filename>java\com\mysql\grt\modules</filename> directory
+ immediately below the installation directory and the
+ <literal>Lua</literal> modules in the <filename>lua</filename>
+ directory. Currently, importing Python modules is not supported.
+ </para>
+
+ <para>
+ To include modules other than the default modules, use the
+ <option>d</option> option with a path.
+ </para>
+
+ <para>
+ It is also possible to use the GRT shell to convert XML files to
+ Java or PHP class files, by opening the shell using the
+ <option>j</option> or the <option>p</option> option and specifying
+ the XML source file and the destination directory.
+ </para>
+
+ <para>
+ Use the <option>listen</option> option with a port number to run
+ the GRT shell as a service that can be accessed from a remote
+ location.
+ </para>
+
+ <para>
+ Perhaps most importantly, you can pass a <literal>Lua</literal>
+ script to the shell on startup. This allows you to perform tasks
+ using a script file without even opening the &workbench; or the
+ &migration_toolkit;. This is an especially useful feature if you
+ need to migrate the same database a number of times or you want to
+ customize a migration. You can easily create a
+ <literal>Lua</literal> script by clicking the <guibutton>Generate
+ Migration Script</guibutton> when migrating using the graphical
+ interface. For information on creating a Lua script see,
+ <xref linkend="mysql-migration-toolkit-indepth-summary"/>. A Lua
+ migration script is examined in detail in
+ <xref linkend="scripted-migration" />.
+ </para>
+
+ <para>
+ Passing a <literal>Lua</literal> file to the shell is usually
+ invoked using the <option>x</option> option so that the shell
+ closes after the script has executed.
+ </para>
+
+ <para>
+ The appearance of the GRT shell run from the command line is
+ identical to its appearance when run from within the &workbench;
+ or the &migration_toolkit;. All the commands and options described
+ in <xref linkend="using-grt-shell"/> are available when the GRT
+ shell is invoked from the command line.
+ </para>
+
+ </section>
+
+<!--End Using -->
+
+</chapter>
+<!-- end GRT Shell -->
Property changes on: trunk/th/gui-common/chapter-grt-shell.xml
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/th/gui-common/chapter-options-connections.xml
===================================================================
--- trunk/th/gui-common/chapter-options-connections.xml (rev 0)
+++ trunk/th/gui-common/chapter-options-connections.xml 2007-10-30 12:01:51 UTC (rev 8401)
Changed blocks: 1, Lines Added: 296, Lines Deleted: 0; 10630 bytes
@@ -0,0 +1,296 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+ <!ENTITY % all.entities SYSTEM "all-entities.ent">
+ %all.entities;
+]>
+<section id="mysql-gui-options-connections">
+
+ <title>Connections</title>
+
+ <para>
+ The <literal>Connections</literal> section allows you to create,
+ edit, and delete connection profiles. The center box displays a list
+ of currently available profiles, together with a history of
+ connections that were made without being stored in a profile. You
+ can collapse or expand both the <literal>Connections</literal> and
+ <literal>History</literal> trees by double clicking them.
+
