Author: shinz
Date: 2006-12-14 22:01:23 +0100 (Thu, 14 Dec 2006)
New Revision: 4265
Log:
Add directory for Romanian translation of MySQL Administrator manual
Added:
trunk/administrator-ro/Makefile
trunk/administrator-ro/Makefile.ext
trunk/administrator-ro/README.for-translators.txt
trunk/administrator-ro/VERSION
trunk/administrator-ro/administrator.xml
trunk/administrator-ro/backup.xml
trunk/administrator-ro/catalogs.xml
trunk/administrator-ro/chapter-options-administrator.xml
trunk/administrator-ro/connection-dialog.xml
trunk/administrator-ro/copyright.xml
trunk/administrator-ro/health.xml
trunk/administrator-ro/images/backup-completed.png
trunk/administrator-ro/images/backup-content.png
trunk/administrator-ro/images/backup-progress.png
trunk/administrator-ro/images/configure-service-mode-connection.png
trunk/administrator-ro/images/configure-service-mode-window.png
trunk/administrator-ro/images/connection.png
trunk/administrator-ro/images/error.png
trunk/administrator-ro/images/graph-settings.png
trunk/administrator-ro/images/mainwindow.png
trunk/administrator-ro/images/marked-area.png
trunk/administrator-ro/images/options-connections.png
trunk/administrator-ro/images/options-general-options.png
trunk/administrator-ro/images/replication.png
trunk/administrator-ro/images/restore-content.png
trunk/administrator-ro/images/server-logs-general-log.png
trunk/administrator-ro/images/system-tray.png
trunk/administrator-ro/images/user-accounts.png
trunk/administrator-ro/images/user-information.png
trunk/administrator-ro/introduction.xml
trunk/administrator-ro/legalnotice.en.xml
trunk/administrator-ro/main-window.xml
trunk/administrator-ro/main-window.xml.orig
trunk/administrator-ro/metadata/administrator.idmap
trunk/administrator-ro/metadata/backup.idmap
trunk/administrator-ro/metadata/catalogs.idmap
trunk/administrator-ro/metadata/chapter-options-administrator.idmap
trunk/administrator-ro/metadata/connection-dialog.idmap
trunk/administrator-ro/metadata/copyright.idmap
trunk/administrator-ro/metadata/health.idmap
trunk/administrator-ro/metadata/introduction.idmap
trunk/administrator-ro/metadata/legalnotice.en.idmap
trunk/administrator-ro/metadata/main-window.idmap
trunk/administrator-ro/metadata/replication-status.idmap
trunk/administrator-ro/metadata/restore.idmap
trunk/administrator-ro/metadata/server-connections.idmap
trunk/administrator-ro/metadata/server-information.idmap
trunk/administrator-ro/metadata/server-logs.idmap
trunk/administrator-ro/metadata/service-control.idmap
trunk/administrator-ro/metadata/startup-variables.idmap
trunk/administrator-ro/metadata/tray-monitor.idmap
trunk/administrator-ro/metadata/user-administration.idmap
trunk/administrator-ro/metadata/xml-files.idmap
trunk/administrator-ro/renamed-nodes.txt
trunk/administrator-ro/replication-status.xml
trunk/administrator-ro/restore.xml
trunk/administrator-ro/server-connections.xml
trunk/administrator-ro/server-information.xml
trunk/administrator-ro/server-logs.xml
trunk/administrator-ro/service-control.xml
trunk/administrator-ro/startup-variables.xml
trunk/administrator-ro/tray-monitor.xml
trunk/administrator-ro/user-administration.xml
trunk/administrator-ro/xml-files.xml
Property changes on: trunk/administrator-ro/README.for-translators.txt
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/administrator-ro/connection-dialog.xml
___________________________________________________________________
Name: svn:executable
+ *
Property changes on: trunk/administrator-ro/images/backup-completed.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/backup-content.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/backup-progress.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/configure-service-mode-connection.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/configure-service-mode-window.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/connection.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/error.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/graph-settings.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/mainwindow.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/marked-area.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/options-connections.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/options-general-options.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/replication.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/restore-content.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/server-logs-general-log.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/system-tray.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/user-accounts.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/administrator-ro/images/user-information.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/administrator-ro/Makefile
===================================================================
--- trunk/administrator-ro/Makefile (rev 0)
+++ trunk/administrator-ro/Makefile 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 67, Lines Deleted: 0; 3591 bytes
@@ -0,0 +1,67 @@
+# 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 = . ../gui-common ../refman-5.1 ../refman-common
+IDMAP_SRCS = $(ADMINISTRATOR_SRCS)
+IDMAP_OBJS = $(call xmllist_to_idmaplist,$(IDMAP_SRCS))
+
+# 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
+
+# Document dependency specifications
+# "make depend" updates the _SRCS variable
+# Set _SRCS_EXTRA variable by hand to any entity files needed
+
+depend:: administrator.depend
+
+ADMINISTRATOR_SRCS_EXTRA = ../common/fixedchars.ent ../gui-common/gui-common.ent
+
+ADMINISTRATOR_SRCS = $(ADMINISTRATOR_SRCS_EXTRA) administrator.xml backup.xml catalogs.xml chapter-options-administrator.xml connection-dialog.xml copyright.xml ../gui-common/appendix-common-files.xml ../gui-common/appendix-connection-storage.xml ../gui-common/appendix-source-install.xml ../gui-common/appendix-third-party.xml ../gui-common/appendix-translator-notes.xml ../gui-common/appendix-troubleshooting.xml ../gui-common/chapter-options-connections.xml ../gui-common/chapter-options-editors.xml ../gui-common/chapter-options-general.xml ../gui-common/chapter-options-introduction.xml ../gui-common/chapter-table-editor.xml ../gui-common/chapter-uninstall-all.xml ../gui-common/images/columneditor.png ../gui-common/images/confirmchanges.png ../gui-common/images/connectionerror.png ../gui-common/images/indexeditor.png ../gui-common/images/options-connection.png ../gui-common/images/options.png ../gui-common/images/tableeditor.png ../gui-common/installation-all.xml ../gui-commo!
n/starting-all.xml health.xml images/configure-service-mode-connection.png images/configure-service-mode-window.png images/connection.png images/graph-settings.png images/mainwindow.png images/marked-area.png images/replication.png images/restore-content.png images/server-logs-general-log.png images/system-tray.png images/user-accounts.png images/user-information.png introduction.xml legalnotice.en.xml main-window.xml replication-status.xml restore.xml server-connections.xml server-information.xml server-logs.xml service-control.xml startup-variables.xml tray-monitor.xml user-administration.xml xml-files.xml
+
+administrator-prepped.xml: $(ADMINISTRATOR_SRCS) $(IDMAP_OBJS)
+
+# 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 ../gui-common/Makefile.ext
+
Added: trunk/administrator-ro/Makefile.ext
===================================================================
--- trunk/administrator-ro/Makefile.ext (rev 0)
+++ trunk/administrator-ro/Makefile.ext 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 425 bytes
@@ -0,0 +1,5 @@
+# Makefile extensions for operations specific to this directory
+
+../administrator/metadata/%.idmap: ../administrator/%.xml
+ make -C ../administrator idmap
+
Added: trunk/administrator-ro/README.for-translators.txt
===================================================================
--- trunk/administrator-ro/README.for-translators.txt (rev 0)
+++ trunk/administrator-ro/README.for-translators.txt 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 76, Lines Deleted: 0; 4332 bytes
@@ -0,0 +1,76 @@
+************************************************************************
+ Notes for translators
+ Author : Stefan Hinz <stefan@stripped>
+ Created : 2006-03-26
+ Last edited : 2006-03-26
+************************************************************************
+
+Here are the very basics you should keep in mind when translating.
+
+1. UPDATE YOUR COPY OF THE REPOSITORY BEFORE STARTING TO TRANSLATE!
+ Whenever you start or restart your translation, run "svn update"
+ first (or the "Update" command from TortoiseSVN). Otherwise, you may
+ find that others have edited the file you're translating, and you
+ might have to do tedious manual merging to get those edits and your
+ own edits in synchronisation.
+
+2. COMMIT OFTEN!
+ Run "svn commit" (or the "Commit" command from TortoiseSVN) often,
+ at least once per day. This will not only give you a backup of your
+ recent edits, but it will also reduce the probability of having to
+ manually merge changes.
+
+3. USE UNIX-STYLE LINE ENDINGS AND UTF-8!
+ Make sure your editor uses Unix-style line endings, and UTF-8 as the
+ character set. If you're using Notepad++, you find both under the
+ "Format" menu: "Convert to Unix format" and "Code as UTF-8".
+
+4. FORMAT AND VALIDATE YOUR DOCUMENTS BEFORE COMMITTING!
+ You don't have to care about line lengths and things when
+ translating. We provide an easy means to format your document, by
+ just running "make <file-name>.format". It's as easy to validate a
+ document: just run "make <file-name>.valid". For both commands, you
+ need to have "make" and "xmllint" installed. (For most Linux
+ distributions, that's the case. Under Windows, you should use
+ Cygwin for this which has "make" installed by default; you need to
+ install "xmllint" yourself.)
+ A few examples below.
+
+ 4a. make query-browser.format
+ This command formats query-browser.xml and all the files
+ included in that document (<xi:include .../>) so that indentions
+ and other whitespace is set consistently. Lines are wrapped at
+ 72 characters.
+
+ 4b. make query-browser.valid
+ This command validates query-browser.xml and all the files
+ included in that document (<xi:include .../>). If you validate
+ only one of the included files (for example,
+ chapter-options-query-browser.xml), you'll likely get a few
+ errors which are all related to missing targets; for example:
+ make chapter-options-query-browser.valid
+ chapter-options-query-browser.xml:54: element link:
+ validity error : IDREF attribute linkend references an unknown
+ ID "mysql-query-browser-tour-resultarea"
+ You can ignore those IDREF errors.
+
+5. TRANSLATE EVERYTHING EXCEPT THINGS BETWEEN < and > or & and ;!
+ Don't translate XML elements, that is, everything between open and
+ closing angle brackets, for example: <section id="something">.
+ Don't translate XML entities, that is, everything between ampersand
+ and semicolon, for example: &this-is-an-entity;.
+ This often happens with search and replace operations, and will lead
+ to validation errors (see #4 above).
+
+6. TRANSLATE THE FILES IN YOUR RESPECTIVE DIRECTORY!
+ For example, if you're about to translate the MySQL Query Browser
+ into Italian, the respective directory is "query-browser-it".
+ Looks for files ending with .xml or .ent.
+ You may need to translate files in other directories, too (unless
+ other translators have done that already). Look for files that are
+ included in the file you're translating (for example,
+ <xi:include href="../gui-common-it/chapter-table-editor.xml"/>).
+ Regarding images (typically screenshots), things become a bit more
+ complicated. Talk to Stefan before making screenshots of applications
+ in your target language.
+
Property changes on: trunk/administrator-ro/README.for-translators.txt
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/administrator-ro/VERSION
===================================================================
--- trunk/administrator-ro/VERSION (rev 0)
+++ trunk/administrator-ro/VERSION 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 723 bytes
@@ -0,0 +1,13 @@
+date
+Pfad: .
+URL: svn+ssh://shinz@stripped/svn/mysqldoc/trunk/administrator
+Basis des Projektarchivs: svn+ssh://shinz@stripped/svn/mysqldoc
+UUID des Projektarchivs: c493bd56-8c02-0410-a43f-aded7e9288fb
+Revision: 4160
+Knotentyp: Verzeichnis
+Plan: normal
+Letzter Autor: plavin
+Letzte geänderte Rev: 4096
+Letztes Änderungsdatum: 2006-12-01 19:44:22 +0100 (Fr, 01 Dez 2006)
+Eigenschaften zuletzt geändert: 2006-11-10 23:46:12 +0100 (Fr, 10 Nov 2006)
+
Added: trunk/administrator-ro/administrator.xml
===================================================================
--- trunk/administrator-ro/administrator.xml (rev 0)
+++ trunk/administrator-ro/administrator.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 134, Lines Deleted: 0; 4957 bytes
@@ -0,0 +1,134 @@
+<?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 % fixedchars.entities SYSTEM "../common/fixedchars.ent">
+ %fixedchars.entities;
+ <!ENTITY % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+ %gui-common.entities;
+ ]>
+<book id="mysql-administrator" lang="ro">
+
+<!--
+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 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/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="../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"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="chapter-options-administrator.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/administrator-ro/backup.xml
===================================================================
--- trunk/administrator-ro/backup.xml (rev 0)
+++ trunk/administrator-ro/backup.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 304, Lines Deleted: 0; 11463 bytes
@@ -0,0 +1,304 @@
+<?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="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 <literal>Backup Project</literal> 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
+ <literal>Add Date/Time to Backup Files</literal> 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 <literal>Advanced Options</literal> 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>
+ <literal>Lock all tables</literal> 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>
+ <literal>Single transaction</literal> 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>
+ <literal>Normal Backup</literal> 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>
+ <literal>Complete Backup</literal> overrides the table selection
+ made in the <literal>Backup Project</literal> 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 <literal>Output File Options</literal> control 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>
+ <literal>No CREATEs</literal> will supress <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>
+ <literal>No EXTENDED INSERTS</literal> will supress 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>
+ <literal>Add DROP Statements</literal> adds <literal>DROP TABLE
+ IF EXISTS</literal> statements to the backup file.
+ </para>
+
+ <para>
+ <literal>Complete INSERTs</literal> 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>
+ <literal>Comment</literal> writes additional backup information
+ to the backup file in the form of SQL comments.
+ </para>
+
+ <para>
+ <literal>Don't write full path</literal> causes &administrator;
+ to write only the table name in statements, instead of
+ <literal>schema_name.table_name</literal>.
+ </para>
+
+ <para>
+ <literal>Compatibility mode</literal> creates backup files that
+ are compatible with older versions of &administrator;.
+ </para>
+
+ <para>
+ <literal>ANSI Quotes</literal> will cause all table and database
+ names to be quoted with ANSI style double quotes instead of
+ backticks.
+ </para>
+
+ <para>
+ <literal>Disable keys</literal> 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 <literal>Schedule</literal> tab. is used to execute backup
+ operations on a daily, weekly, or monthly basis.
+ </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 <literal>Add Date/Time to Backup
+ Files</literal> option in the <literal>Administrator
+ Options</literal> dialogue, 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 <literal>Time</literal>
+ option. Set the backup time in a 24 hour format (i.e. 23:30).
+ </para>
+
+ <para>
+ When you select the <literal>Execute Backup Weekly</literal>
+ 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
+ immediatly click the <guibutton>Execute Backup Now</guibutton>
+ button.
+ </para>
+
+ </section>
+
+<!-- END SCHEDULE -->
+
+</chapter>
Added: trunk/administrator-ro/catalogs.xml
===================================================================
--- trunk/administrator-ro/catalogs.xml (rev 0)
+++ trunk/administrator-ro/catalogs.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 222, Lines Deleted: 0; 8346 bytes
@@ -0,0 +1,222 @@
+<?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="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 <literal>Schema Tables</literal> and <literal>Schema
+ Indices</literal> 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 <literal>Schema Tables</literal> 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 <literal>Update Time</literal>. 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
+ (<literal>Type</literal>, <literal>Row Format</literal>, 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>
+ <literal>Optimize Table</literal>: 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>
+ <literal>Check Table</literal>: 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>
+ <literal>Repair Table</literal>: 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 <literal>Schema Indices</literal> 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/administrator-ro/chapter-options-administrator.xml
===================================================================
--- trunk/administrator-ro/chapter-options-administrator.xml (rev 0)
+++ trunk/administrator-ro/chapter-options-administrator.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 148, Lines Deleted: 0; 5267 bytes
@@ -0,0 +1,148 @@
+<?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 % fixedchars.entities SYSTEM "../common/fixedchars.ent">
+ %fixedchars.entities;
+ <!ENTITY % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+ %gui-common.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 three
+ 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>
+ <literal>Show Global Privileges</literal>: 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>
+ <literal>Show Table/Column Privileges</literal>: 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>
+ <literal>Use Peak Level Indicator</literal>: This will display
+ a thin yellow line on the health graphs indicating the highest
+ value recorded by the graph.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Reset peak Level after a number of ticks</literal>:
+ 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 <literal>Time
+ after the Peak level resets</literal> 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>
+ <literal>Time after the Peak level resets</literal>: When the
+ <literal>Reset peak Level after a number of ticks</literal>
+ 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>
+ <literal>Add Date/Time to Backup Files</literal>: 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/administrator-ro/connection-dialog.xml
===================================================================
--- trunk/administrator-ro/connection-dialog.xml (rev 0)
+++ trunk/administrator-ro/connection-dialog.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 220, Lines Deleted: 0; 8086 bytes
@@ -0,0 +1,220 @@
+<?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;
+]>
+<!-- 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
+ <link linkend="mysql-administrator-starting-configure-service">configure
+ -service mode</link>.
+ </para>
+
+ <remark>
+ update image
+ </remark>
+
+ <figure>
+ <title>Connection dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/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 appear, telling you that this is not possible.
+ </para>
+
+ <para>
+ If the server connection is successfully established, all of the
+ values filled in the fields of the connection dialog will be saved
+ for future connections (see the section that describes
+ <link linkend="mysql-gui-appendix-store-connections">how
+ &administrator; stores connection information</link>). The
+ <literal>Password</literal> field, however, will always be empty:
+ For security reasons, the password is not stored along with the
+ other options, unless you explicitly specify otherwise in the
+ <link linkend="mysql-gui-options-general-options">General Options
+ section of the Options dialog</link>.
+ </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. When you click the <guibutton>OK</guibutton> button after
+ changing a profile's values, the changes are stored permanently if
+ a successful connection to the MySQL server is established.
+ 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
+ <literal>Options</literal> dialog window that has a
+ <literal>Connections</literal> section for modifying connection
+ profiles. You can find the values you can set in the Connection
+ dialog window in the description of the
+ <literal>Connections</literal> section of the
+ <literal>Options</literal> dialog (see
+ <link linkend="mysql-gui-options-connections">Options
+ dialog</link>).
+ </para>
+
+ </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, at the moment, 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 <link linkend="multiple-servers">multiple
+ servers</link> 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
+ Windows services management. 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.
+ </para>
+ </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 that key is pressed.
+ </para>
+
+ <figure>
+ <title>Switching to configure-service mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/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 the
+ normal mode, thus starting &administrator; in configure-service
+ mode.
+ </para>
+
+ <figure>
+ <title>Configure-service mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/configure-service-mode-window.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Configure-service mode</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ Under <literal>Installed Services</literal> 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. In configure-service mode, not all
+ 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.
+ </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>
+
+ </itemizedlist>
+
+ <para>
+ Both of those sections are described in what follows.
+ </para>
+
+ </section>
+
+<!-- Configure-service Mode -->
+
+</chapter>
Property changes on: trunk/administrator-ro/connection-dialog.xml
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/administrator-ro/copyright.xml
===================================================================
--- trunk/administrator-ro/copyright.xml (rev 0)
+++ trunk/administrator-ro/copyright.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 474 bytes
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+<para>
+ Copyright 2004-2006 MySQL AB
+</para>
Added: trunk/administrator-ro/health.xml
===================================================================
--- trunk/administrator-ro/health.xml (rev 0)
+++ trunk/administrator-ro/health.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 377, Lines Deleted: 0; 14488 bytes
@@ -0,0 +1,377 @@
+<?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="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>
+ <literal>Connection Usage</literal>: 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>
+ <literal>Traffic</literal>: 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>
+ <literal>Number of SQL Queries</literal>: 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>
+ <literal>Query Cache Hitrate</literal>: 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>
+ <literal>Key Efficiency</literal>: 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/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 <literal>Value
+ Unit</literal> 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>
+
+ <remark>
+ [MH] Max FormulaR? Lets get this fixed.
+ </remark>
+
+ </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/administrator-ro/images/backup-completed.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 331 bytes
Added: trunk/administrator-ro/images/backup-content.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 327 bytes
Added: trunk/administrator-ro/images/backup-progress.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 329 bytes
Added: trunk/administrator-ro/images/configure-service-mode-connection.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 365 bytes
Added: trunk/administrator-ro/images/configure-service-mode-window.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 357 bytes
Added: trunk/administrator-ro/images/connection.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 319 bytes
Added: trunk/administrator-ro/images/error.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 309 bytes
Added: trunk/administrator-ro/images/graph-settings.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 327 bytes
Added: trunk/administrator-ro/images/mainwindow.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 319 bytes
Added: trunk/administrator-ro/images/marked-area.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 321 bytes
Added: trunk/administrator-ro/images/options-connections.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 337 bytes
Added: trunk/administrator-ro/images/options-general-options.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 345 bytes
Added: trunk/administrator-ro/images/replication.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 321 bytes
Added: trunk/administrator-ro/images/restore-content.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 329 bytes
Added: trunk/administrator-ro/images/server-logs-general-log.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 345 bytes
Added: trunk/administrator-ro/images/system-tray.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 321 bytes
Added: trunk/administrator-ro/images/user-accounts.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 325 bytes
Added: trunk/administrator-ro/images/user-information.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 331 bytes
Added: trunk/administrator-ro/introduction.xml
===================================================================
--- trunk/administrator-ro/introduction.xml (rev 0)
+++ trunk/administrator-ro/introduction.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 66, Lines Deleted: 0; 2220 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 % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+ %gui-common.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/administrator-ro/legalnotice.en.xml
===================================================================
--- trunk/administrator-ro/legalnotice.en.xml (rev 0)
+++ trunk/administrator-ro/legalnotice.en.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1787 bytes
@@ -0,0 +1,32 @@
+<?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>
+
+ <xi:include href="copyright.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <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>
+ Please email <email>docs@stripped</email> for more information or
+ if you are interested in doing a translation.
+ </para>
+
+</legalnotice>
Added: trunk/administrator-ro/main-window.xml
===================================================================
--- trunk/administrator-ro/main-window.xml (rev 0)
+++ trunk/administrator-ro/main-window.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 427, Lines Deleted: 0; 13657 bytes
@@ -0,0 +1,427 @@
+<?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;
+ ]>
+<!-- Starting &administrator; -->
+<chapter id="mysql-administrator-main-window">
+
+ <title>Fereastra Principală</title>
+
+ <section id="mysql-administrator-main-window-introduction">
+
+ <title>Introducere</title>
+
+ <para>
+ Dupa ce aţi deschis cu succes o conexiune la serverul MySQL, apare fereastra principală a aplicaţiei &administrator;(vezi imagine). Fereastra principală conţine o bara laterală, o
+ fereastra de lucru, meniuri cu submeniuri.
+ </para>
+
+ <remark>
+ [SH] add annotations!)
+ </remark>
+
+ <figure>
+ <title> Fereastra principală a aplicaţiei &administrator;</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/mainwindow.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Fereastra principală a aplicaţiei &administrator; </phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-sidebar">
+
+ <title>Bara laterală </title>
+
+ <para>
+ Bara laterală permite accesul la următoarele secţiuni:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-server-information">Server
+ Information</link>: Informaţii privind serverul MySQL la care este deschisă conexiunea, &administrator; sistemul pe care ruleaza aplicaţia, conexiunea deschisa.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-service-control">Service
+ Control</link>: Pornirea / oprirea serverul MySQL. Dacă atat
+ &administrator; cat şi serverul MySQL rulează pe sisteme Windows, MySQL poate fi configurat ca şi serviciu pe sistemul Windows.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-startup-variables">Startup
+ Variables</link>: Configurarea variabilelor de startup ale serverului MySQL.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-server-connections">Server
+ Connections</link>: Vizualizarea sau oprirea conexiunilor curente la serverul MySQL (denumite threads).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-user-administration">User
+ Administration</link>: Adminstrarea utilizatorilor, adăugare utilizator nou
+ , sau stergere utilizatori existenţi.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-health">Health</link>:
+ Afisarea grafică a valorilor de utilizare care afectează performanţa serverului, o vedere ierarhică a variabilelor de sistem şi de stare.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-server-logs">Server
+ Logs</link>: Vizualizarea intrărilor din fişierele de log.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-backup">Backup</link>:
+ Planificarea şi administrarea proiectelor de backup, selectarea bazelor de date la care se vor face copii de sigurantă(backup), pornirea procesului de backup.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link
+linkend="mysql-administrator-restore">Restore</link>:
+ Restaurarea bazelor de date din copiile de siguranţa(backups) existente.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-replication-status">Replication
+ Status</link>: Vizualizarea informatiilor privind serverul master şi serverele
+ slave (replici).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <link linkend="mysql-administrator-catalogs">Catalogs</link>:
+ Vizualizarea informatiilor privind bazele de date, tabele, coloane, index-uri,
+ şi randuri; optimizare tabele.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Secţiunile urmatoare descriu in detaliu fiecare termen.
+ </para>
+
+ <para>
+ Poţi schimba lăţimea barei laterale din fereastra principală prin mutarea separatorului aflat intre bara laterală şi fereastra de lucru.
+ Pentru a ascunde complet bara laterală, execută click pe zona marcată a separatorului (mijlocul separatorului). Pentru a face bara laterală vizibilă din nou, executa dublu click pe zona marcată (care acum este situată pe marginea din stanga a ferestrei principale).
+ </para>
+
+ <figure>
+ <title>Zona marcată intre bara laterală şi fereastra de lucru</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/marked-area.png" format="PNG" lang="en"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Zona marcată intre bara laterală şi fereastra de lucru
+ </phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+<!-- Sidebar -->
+
+ <section id="mysql-administrator-working-area">
+
+ <title>Fereastra de lucru</title>
+
+ <para>
+ In timp ce
+ <link linkend="mysql-administrator-sidebar">bara laterală</link> permite
+ selectarea anumitor sectiuni, fereastra de lucru afisează informatii, sau
+ campuri, referitoare la sectiunile selectate. Pentru unele sectiuni,
+ fereastra de lucru este impartită in două sau mai multe tab-uri.
+ </para>
+
+ </section>
+
+<!-- Working Area -->
+
+ <section id="mysql-administrator-menus">
+
+ <title>Meniuri</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>
+ Deschide fereastra de dialog
+ <link linkend="mysql-administrator-starting-connection">Connection
+ </link>, şi permite stabilirea unei conexiuni la un alt server MySQL. Pot fi deschise simultan mai multe conexiuni.
+ MySQL Administrator deschide o noua fereastră principala pentru fiecare conexiune stabilită. Conexiunile pot fi stabilite la unul sau mai multe servere MySQL. Conexiunile pot fi deschise folosind acelaşi profil precum şi cu profile diferite.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-file-manage-connections">
+
+ <title>Reconnect</title>
+
+ <para>
+ Această opţiune inchide conexiunea curentă şi deschide fereastra de dialog
+ <link linkend="mysql-gui-options">Options</link>, cu sectiunea
+ <link
+linkend="mysql-gui-options-connections">Connections
+ </link> preselectată.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-copy-active-page">
+
+ <title>Copy Active Page as Text ...</title>
+
+ <para>
+ Această opţiune permite copierea informatiilor afisate in pagina
+ <literal>Server Information</literal> in clipboard.
+ Pentru mai multe informatii privind pagina <literal>Server
+ Information</literal> vezi
+ <xref linkend="mysql-administrator-server-information" />.
+ </para>
+
+
+ <note>
+ <para>
+ <remark>
+ Not Linux. Mac OS X?
+ </remark>
+ Această opţiune, valabilă doar pe sistemele Windows,
+ permite copierea informatiilor prezente in sectiunea <literal>Server Information</literal>.
+ </para>
+ </note>
+
+ </section>
+
+ <section id="mysql-administrator-menus-file-save-current-connection">
+
+ <title>Save current Connection ...</title>
+
+ <para>
+ Deschide <link linkend="mysql-gui-options">fereastra de dialog Options</link>, in interiorul ferestrei
+ <link
+linkend="mysql-gui-options-connections">Connections
+ </link>. Simultan, un nou profil de conexiune denumit
+ <literal>New Connection</literal> este creat.
+ Campurile sunt completate cu setările ultimei conexiuni utilizate. Poţi modifica aceste valori şi să salvezi setările in noul profil.
+ Deasemenea poţi schimba denumirea noului profil creat
+ din <literal>New Connection</literal>intr-un nume adecvat. Daca acţionezi butonul
+ <guibutton>Close</guibutton> fara a salva modificările
+ folosind butonul <guibutton>Apply Changes</guibutton>,
+ vei fi intrebat daca vrei să sălvezi sau nu modificările efectuate.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-file-close">
+
+ <title>Close</title>
+
+ <para>
+ Inchide fereastra aplicaţiei &administrator; precum şi conexiunea la serverul MySQL care a fost stabilită in acea fereastră. Dacă aţi deschis mai multe instanţe ale aplicatiei &administrator; (ferestre sau procese), această comandă nu va inchide celelalte ferestre.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- File -->
+
+ <section id="mysql-administrator-menus-edit">
+
+ <title>Edit</title>
+
+ <para>
+ Comenzile <guimenu>Cut</guimenu>, <guimenu>Copy</guimenu>, şi
+ <guimenu>Paste</guimenu> permit tăierea, copierea, sau
+ lipirea textului selectat in
+ <link linkend="mysql-administrator-working-area">fereastra
+ de lucru</link>.
+ </para>
+
+ <section id="mysql-administrator-menus-edit-options">
+
+ <title>Options</title>
+
+ <para>
+ Deschide fereastra de dialog <link linkend="mysql-gui-options">Options
+ </link>.
+ </para>
+
+ </section>
+
+<!-- Options -->
+
+ </section>
+
+<!-- Edit -->
+
+ <section id="mysql-administrator-menus-view">
+
+ <title>View</title>
+
+ <remark>
+ Must be consistent options or sections?
+ </remark>
+
+ <para>
+ Meniul <guimenu>View</guimenu> permite selectarea unei secţiuni din
+ <link linkend="mysql-administrator-sidebar">bara laterală</link>.
+ Selectarea unui element din acest meniu are acelaşi efect ca şi selectarea sectiunii cu acelaşi nume din bara laterală.
+ </para>
+
+ </section>
+
+<!-- View -->
+
+ <section id="mysql-administrator-menus-tools">
+
+ <title>Tools</title>
+
+ <para>
+ Meniul <guimenu>Tools</guimenu> porneşte alte programe.
+ </para>
+
+ <section
+id="mysql-administrator-menus-tools-mysql-command-line-client">
+
+ <title>MySQL Command Line Client</title>
+
+ <para>
+ Acestă opţiune este disponibilă doar dacă &administrator; găseşte executabilul
+ clientului MySQL in linia de comandă(mysql). In acest moment, căutarea are loc in locatii ca
+ <literal>C:\mysql\bin</literal>,
+ <literal>D:\mysql\bin</literal>, şi
+ <literal>C:\<replaceable>program
+ directory</replaceable>\mysql\bin</literal> pentru a găsi
+ <literal>mysql.exe</literal>. Dacă executabilul este găsit,
+ clientul in linia de comandă poate fi lansat cu această opţiune din meniu.
+ &administrator; va folosi informaţiile pe care le-ai furnizat in fereastra de dialog
+ <link linkend="mysql-administrator-starting-connection">Connection
+ </link> pentru a stabili o conexiune la server folosind clientul in linia de comandă.
+ </para>
+
+ </section>
+
+ <section
+id="mysql-administrator-menus-tools-windows-command-line">
+
+ <title>Windows Command Line</title>
+
+ <para>
+ Deschide o fereastră de comenzi.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- Tools -->
+
+ <section id="mysql-administrator-menus-help">
+
+ <title>Help</title>
+
+ <section id="mysql-administrator-menus-help-online-help">
+
+ <title>Online Help</title>
+
+ <para>
+ Deschide o fereastră ce afişează secţiunea &administrator; din manualul de referinţă MySQL.
+
+ <remark>
+ [SH] Mike: Should be "Help" only to make clear it will not
+ load the MySQL online manual from www.mysql.com/doc/
+ </remark>
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-help-report-bug">
+
+ <title>Report Bug to MySQL</title>
+
+ <para>
+ Deschide in fereastra browserului o conexiune la sistemul MySQL de raportare a erorilor.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-help-mysql-website">
+
+ <title>Launch MySQL Website</title>
+
+ <para>
+ Deschide in fereastra browserului o conexiune la site-ul MySQL.
+ </para>
+
+ </section>
+
+ <section id="mysql-administrator-menus-help-about">
+
+ <title>About ...</title>
+
+ <para>
+ Afişează informaţii despre &administrator;.
+ </para>
+
+ </section>
+
+ </section>
+
+<!-- Help -->
+
+ </section>
+
+<!-- Menus -->
+
+</chapter>
Added: trunk/administrator-ro/main-window.xml.orig
===================================================================
--- trunk/administrator-ro/main-window.xml.orig (rev 0)
+++ trunk/administrator-ro/main-window.xml.orig 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 457, Lines Deleted: 0; 13179 bytes
@@ -0,0 +1,457 @@
+<?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;
+ ]>
+<!-- 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/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/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 <literal>New Connection</literal> is created,
+ which 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 <literal>New Connection</literal> 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 <literal>C:\mysql\bin</literal>,
+ <literal>D:\mysql\bin</literal>, and
+ <literal>C:\<replaceable>program
+ directory</replaceable>\mysql\bin</literal> 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>Online Help</title>
+
+ <para>
+ Opens a window displaying the &administrator; section of the
+ MySQL reference manual.
+
+ <remark>
+ [SH] Mike: Should be "Help" only to make clear it will not
+ load the MySQL online manual from www.mysql.com/doc/
+ </remark>
+ </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/administrator-ro/metadata/administrator.idmap
===================================================================
--- trunk/administrator-ro/metadata/administrator.idmap (rev 0)
+++ trunk/administrator-ro/metadata/administrator.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 0; 507 bytes
@@ -0,0 +1,2 @@
+mysql-administrator:book:mysql-administrator:administrator.xml:administrator/en:&administrator;
+mysql-gui-options:chapter:mysql-gui-options:administrator.xml:administrator/en:Options Dialog
Added: trunk/administrator-ro/metadata/backup.idmap
===================================================================
--- trunk/administrator-ro/metadata/backup.idmap (rev 0)
+++ trunk/administrator-ro/metadata/backup.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 1275 bytes
@@ -0,0 +1,7 @@
+mysql-administrator-backup:chapter:mysql-administrator-backup:backup.xml:administrator/en:Backup
+mysql-administrator-backup-advanced-options:section:mysql-administrator-backup-backup-project:backup.xml:administrator/en:Advanced Options
+mysql-administrator-backup-advanced-options-execution-method:section:mysql-administrator-backup-advanced-options:backup.xml:administrator/en:Backup Execution Method
+mysql-administrator-backup-advanced-options-output-options:section:mysql-administrator-backup-advanced-options-execution-method:backup.xml:administrator/en:Output File Options
+mysql-administrator-backup-backup-project:section:mysql-administrator-backup-introduction:backup.xml:administrator/en:Backup Project
+mysql-administrator-backup-introduction:section:mysql-administrator-backup-introduction:backup.xml:administrator/en:Introduction
+mysql-administrator-backup-schedule:section:mysql-administrator-backup-advanced-options-output-options:backup.xml:administrator/en:Schedule
Added: trunk/administrator-ro/metadata/catalogs.idmap
===================================================================
--- trunk/administrator-ro/metadata/catalogs.idmap (rev 0)
+++ trunk/administrator-ro/metadata/catalogs.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 1132 bytes
@@ -0,0 +1,6 @@
+mysql-administrator-catalogs:chapter:mysql-administrator-catalogs:catalogs.xml:administrator/en:Catalogs
+mysql-administrator-catalogs-indexes:section:mysql-administrator-catalogs-schema-tables-row-status:catalogs.xml:administrator/en:Schema Indexes
+mysql-administrator-catalogs-introduction:section:mysql-administrator-catalogs-introduction:catalogs.xml:administrator/en:Introduction
+mysql-administrator-catalogs-schema-tables:section:mysql-administrator-catalogs-introduction:catalogs.xml:administrator/en:Schema Tables
+mysql-administrator-catalogs-schema-tables-row-status:section:mysql-administrator-catalogs-schema-tables-table-status:catalogs.xml:administrator/en:Row Status
+mysql-administrator-catalogs-schema-tables-table-status:section:mysql-administrator-catalogs-schema-tables:catalogs.xml:administrator/en:Table Status
Added: trunk/administrator-ro/metadata/chapter-options-administrator.idmap
===================================================================
--- trunk/administrator-ro/metadata/chapter-options-administrator.idmap (rev 0)
+++ trunk/administrator-ro/metadata/chapter-options-administrator.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 987 bytes
@@ -0,0 +1,4 @@
+mysql-gui-options-administrator:section:mysql-gui-options-administrator:chapter-options-administrator.xml:administrator/en:Administrator
+mysql-gui-options-administrator-backup:section:mysql-gui-options-administrator-health-graphs:chapter-options-administrator.xml:administrator/en:Backup
+mysql-gui-options-administrator-health-graphs:section:mysql-gui-options-administrator-user-administration:chapter-options-administrator.xml:administrator/en:Health Graphs
+mysql-gui-options-administrator-user-administration:section:mysql-gui-options-administrator:chapter-options-administrator.xml:administrator/en:User Administration
Added: trunk/administrator-ro/metadata/connection-dialog.idmap
===================================================================
--- trunk/administrator-ro/metadata/connection-dialog.idmap (rev 0)
+++ trunk/administrator-ro/metadata/connection-dialog.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 0; 754 bytes
@@ -0,0 +1,3 @@
+mysql-administrator-starting:chapter:mysql-administrator-starting:connection-dialog.xml:administrator/en:Connection Dialog
+mysql-administrator-starting-configure-service:section:mysql-administrator-starting-connection:connection-dialog.xml:administrator/en:Configure-service Mode
+mysql-administrator-starting-connection:section:mysql-administrator-starting-connection:connection-dialog.xml:administrator/en:Connection Dialog
Added: trunk/administrator-ro/metadata/copyright.idmap
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 121 bytes
Added: trunk/administrator-ro/metadata/health.idmap
===================================================================
--- trunk/administrator-ro/metadata/health.idmap (rev 0)
+++ trunk/administrator-ro/metadata/health.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 1228 bytes
@@ -0,0 +1,7 @@
+mysql-administrator-health:chapter:mysql-administrator-health:health.xml:administrator/en:Health
+mysql-administrator-health-connection-health:section:mysql-administrator-health-introduction:health.xml:administrator/en:Connection Health
+mysql-administrator-health-creating-graphs:section:mysql-administrator-health-memory-health:health.xml:administrator/en:Creating Custom Health Graphs
+mysql-administrator-health-introduction:section:mysql-administrator-health-introduction:health.xml:administrator/en:Introduction
+mysql-administrator-health-memory-health:section:mysql-administrator-health-connection-health:health.xml:administrator/en:Memory Health
+mysql-administrator-health-status-variables:section:mysql-administrator-health-creating-graphs:health.xml:administrator/en:Status Variables
+mysql-administrator-health-system-variables:section:mysql-administrator-health-status-variables:health.xml:administrator/en:System Variables
Added: trunk/administrator-ro/metadata/introduction.idmap
===================================================================
--- trunk/administrator-ro/metadata/introduction.idmap (rev 0)
+++ trunk/administrator-ro/metadata/introduction.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 452 bytes
@@ -0,0 +1 @@
+mysql-administrator-introduction:chapter:mysql-administrator-introduction:introduction.xml:administrator/en:Introduction to &administrator;
Added: trunk/administrator-ro/metadata/legalnotice.en.idmap
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 126 bytes
Added: trunk/administrator-ro/metadata/main-window.idmap
===================================================================
--- trunk/administrator-ro/metadata/main-window.idmap (rev 0)
+++ trunk/administrator-ro/metadata/main-window.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 22, Lines Deleted: 0; 3273 bytes
@@ -0,0 +1,22 @@
+mysql-administrator-main-window:chapter:mysql-administrator-main-window:main-window.xml:administrator/en:Main Window
+mysql-administrator-main-window-introduction:section:mysql-administrator-main-window-introduction:main-window.xml:administrator/en:Introduction
+mysql-administrator-menus:section:mysql-administrator-working-area:main-window.xml:administrator/en:Menus
+mysql-administrator-menus-copy-active-page:section:mysql-administrator-menus-file-manage-connections:main-window.xml:administrator/en:Copy Active Page as Text ...
+mysql-administrator-menus-edit:section:mysql-administrator-menus-file-close:main-window.xml:administrator/en:Edit
+mysql-administrator-menus-edit-options:section:mysql-administrator-menus-edit:main-window.xml:administrator/en:Options
+mysql-administrator-menus-file:section:mysql-administrator-menus:main-window.xml:administrator/en:File
+mysql-administrator-menus-file-close:section:mysql-administrator-menus-file-save-current-connection:main-window.xml:administrator/en:Close
+mysql-administrator-menus-file-manage-connections:section:mysql-administrator-menus-file-new-instance-connection:main-window.xml:administrator/en:Reconnect
+mysql-administrator-menus-file-new-instance-connection:section:mysql-administrator-menus-file:main-window.xml:administrator/en:New Instance Connection ...
+mysql-administrator-menus-file-save-current-connection:section:mysql-administrator-menus-copy-active-page:main-window.xml:administrator/en:Save current Connection ...
+mysql-administrator-menus-help:section:mysql-administrator-menus-tools-windows-command-line:main-window.xml:administrator/en:Help
+mysql-administrator-menus-help-about:section:mysql-administrator-menus-help-mysql-website:main-window.xml:administrator/en:About ...
+mysql-administrator-menus-help-mysql-website:section:mysql-administrator-menus-help-report-bug:main-window.xml:administrator/en:Launch MySQL Website
+mysql-administrator-menus-help-online-help:section:mysql-administrator-menus-help:main-window.xml:administrator/en:Online Help
+mysql-administrator-menus-help-report-bug:section:mysql-administrator-menus-help-online-help:main-window.xml:administrator/en:Report Bug to MySQL
+mysql-administrator-menus-tools:section:mysql-administrator-menus-view:main-window.xml:administrator/en:Tools
+mysql-administrator-menus-tools-mysql-command-line-client:section:mysql-administrator-menus-tools:main-window.xml:administrator/en:MySQL Command Line Client
+mysql-administrator-menus-tools-windows-command-line:section:mysql-administrator-menus-tools-mysql-command-line-client:main-window.xml:administrator/en:Windows Command Line
+mysql-administrator-menus-view:section:mysql-administrator-menus-edit-options:main-window.xml:administrator/en:View
+mysql-administrator-sidebar:section:mysql-administrator-main-window-introduction:main-window.xml:administrator/en:Sidebar
+mysql-administrator-working-area:section:mysql-administrator-sidebar:main-window.xml:administrator/en:Working Area
Added: trunk/administrator-ro/metadata/replication-status.idmap
===================================================================
--- trunk/administrator-ro/metadata/replication-status.idmap (rev 0)
+++ trunk/administrator-ro/metadata/replication-status.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 981 bytes
@@ -0,0 +1,4 @@
+mysql-administrator-replication-introduction:section:mysql-administrator-replication-introduction:replication-status.xml:administrator/en:Introduction
+mysql-administrator-replication-status:chapter:mysql-administrator-replication-status:replication-status.xml:administrator/en:Replication Status
+mysql-administrator-replication-status-configure:section:mysql-administrator-replication-introduction:replication-status.xml:administrator/en:Configuring Replication Servers
+mysql-administrator-replication-status-using:section:mysql-administrator-replication-status-configure:replication-status.xml:administrator/en:Using the Replication Status Section
Added: trunk/administrator-ro/metadata/restore.idmap
===================================================================
--- trunk/administrator-ro/metadata/restore.idmap (rev 0)
+++ trunk/administrator-ro/metadata/restore.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 795 bytes
@@ -0,0 +1,4 @@
+mysql-administrator-restore:chapter:mysql-administrator-restore:restore.xml:administrator/en:Restore
+mysql-administrator-restore-general:section:mysql-administrator-restore-introduction:restore.xml:administrator/en:The General Tab
+mysql-administrator-restore-introduction:section:mysql-administrator-restore-introduction:restore.xml:administrator/en:Introduction
+mysql-administrator-restore-restore-content:section:mysql-administrator-restore-general:restore.xml:administrator/en:Restore Content
Added: trunk/administrator-ro/metadata/server-connections.idmap
===================================================================
--- trunk/administrator-ro/metadata/server-connections.idmap (rev 0)
+++ trunk/administrator-ro/metadata/server-connections.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 965 bytes
@@ -0,0 +1,4 @@
+mysql-administrator-server-connections:chapter:mysql-administrator-server-connections:server-connections.xml:administrator/en:Server Connections
+mysql-administrator-server-connections-introduction:section:mysql-administrator-server-connections-introduction:server-connections.xml:administrator/en:Introduction
+mysql-administrator-server-connections-threads:section:mysql-administrator-server-connections-introduction:server-connections.xml:administrator/en:Threads
+mysql-administrator-server-connections-user-connections:section:mysql-administrator-server-connections-threads:server-connections.xml:administrator/en:User Connections
Added: trunk/administrator-ro/metadata/server-information.idmap
===================================================================
--- trunk/administrator-ro/metadata/server-information.idmap (rev 0)
+++ trunk/administrator-ro/metadata/server-information.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 475 bytes
@@ -0,0 +1 @@
+mysql-administrator-server-information:chapter:mysql-administrator-server-information:server-information.xml:administrator/en:Server Information
Added: trunk/administrator-ro/metadata/server-logs.idmap
===================================================================
--- trunk/administrator-ro/metadata/server-logs.idmap (rev 0)
+++ trunk/administrator-ro/metadata/server-logs.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 981 bytes
@@ -0,0 +1,5 @@
+mysql-administrator-server-logs:chapter:mysql-administrator-server-logs:server-logs.xml:administrator/en:Server Logs
+mysql-administrator-server-logs-error-log:section:mysql-administrator-server-logs-introduction:server-logs.xml:administrator/en:Error Log
+mysql-administrator-server-logs-general-log:section:mysql-administrator-server-logs-slow-log:server-logs.xml:administrator/en:General Log
+mysql-administrator-server-logs-introduction:section:mysql-administrator-server-logs-introduction:server-logs.xml:administrator/en:Introduction
+mysql-administrator-server-logs-slow-log:section:mysql-administrator-server-logs-error-log:server-logs.xml:administrator/en:Slow Log
Added: trunk/administrator-ro/metadata/service-control.idmap
===================================================================
--- trunk/administrator-ro/metadata/service-control.idmap (rev 0)
+++ trunk/administrator-ro/metadata/service-control.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 952 bytes
@@ -0,0 +1,4 @@
+mysql-administrator-service-control:chapter:mysql-administrator-service-control:service-control.xml:administrator/en:Service Control
+mysql-administrator-service-control-configure-service:section:mysql-administrator-service-control-start-stop-service:service-control.xml:administrator/en:Configure Service
+mysql-administrator-service-control-introduction:section:mysql-administrator-service-control-introduction:service-control.xml:administrator/en:Introduction
+mysql-administrator-service-control-start-stop-service:section:mysql-administrator-service-control-introduction:service-control.xml:administrator/en:Start/Stop Service
Added: trunk/administrator-ro/metadata/startup-variables.idmap
===================================================================
--- trunk/administrator-ro/metadata/startup-variables.idmap (rev 0)
+++ trunk/administrator-ro/metadata/startup-variables.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 0; 632 bytes
@@ -0,0 +1,2 @@
+mysql-administrator-startup-variables:chapter:mysql-administrator-startup-variables:startup-variables.xml:administrator/en:Startup Variables
+mysql-administrator-startup-variables-introduction:section:mysql-administrator-startup-variables-introduction:startup-variables.xml:administrator/en:Introduction
Added: trunk/administrator-ro/metadata/tray-monitor.idmap
===================================================================
--- trunk/administrator-ro/metadata/tray-monitor.idmap (rev 0)
+++ trunk/administrator-ro/metadata/tray-monitor.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 458 bytes
@@ -0,0 +1 @@
+mysql-administrator-appendix-tray-monitor:appendix:mysql-administrator-appendix-tray-monitor:tray-monitor.xml:administrator/en:The &tray_monitor;
Added: trunk/administrator-ro/metadata/user-administration.idmap
===================================================================
--- trunk/administrator-ro/metadata/user-administration.idmap (rev 0)
+++ trunk/administrator-ro/metadata/user-administration.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 1559 bytes
@@ -0,0 +1,7 @@
+mysql-administrator-user-administration:chapter:mysql-administrator-user-administration:user-administration.xml:administrator/en:User Administration
+mysql-administrator-user-administration-global-privileges:section:mysql-administrator-user-administration-user-information:user-administration.xml:administrator/en:Global Privileges
+mysql-administrator-user-administration-introduction:section:mysql-administrator-user-administration-introduction:user-administration.xml:administrator/en:Introduction
+mysql-administrator-user-administration-schema-privileges:section:mysql-administrator-user-administration-global-privileges:user-administration.xml:administrator/en:Schema Privileges
+mysql-administrator-user-administration-table-column-privileges:section:mysql-administrator-user-administration-schema-privileges:user-administration.xml:administrator/en:Table Column Privileges
+mysql-administrator-user-administration-user-accounts:section:mysql-administrator-user-administration-introduction:user-administration.xml:administrator/en:User Accounts
+mysql-administrator-user-administration-user-information:section:mysql-administrator-user-administration-user-accounts:user-administration.xml:administrator/en:User Information
Added: trunk/administrator-ro/metadata/xml-files.idmap
===================================================================
--- trunk/administrator-ro/metadata/xml-files.idmap (rev 0)
+++ trunk/administrator-ro/metadata/xml-files.idmap 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 455 bytes
@@ -0,0 +1 @@
+mysql-administrator-appendix-xml-files:appendix:mysql-administrator-appendix-xml-files:xml-files.xml:administrator/en:XML Files Used by &administrator;
Added: trunk/administrator-ro/renamed-nodes.txt
===================================================================
--- trunk/administrator-ro/renamed-nodes.txt (rev 0)
+++ trunk/administrator-ro/renamed-nodes.txt 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1194 bytes
@@ -0,0 +1,20 @@
+# renamed-nodes.txt
+#
+# This file lists page name changes for online multi-page documents.
+# These are documents that are built with a command of the form "make
+# docname.html-web". For such documents, page names correspond to
+# the root element id in the DocBook source for the page. For example,
+# <section id="this-is-a-page"> generates a page named this-is-a-page.html.
+# If the section id changes, list the old and new id values in this
+# file so that the mysql.com web server knows how to map requests for
+# the old page to the new page. Each mapping line lists the old id
+# followed by the new id, separated by a space.
+# Example: my-old-page-name my-new-page-name
+# When the .html-web target for the document is built and transferred
+# to the web server host, this file is packaged with the output HTML
+# pages.
+#
+#
+# Lines beginning with # in column one are interpreted as
+# comments and ignored.
+#
Added: trunk/administrator-ro/replication-status.xml
===================================================================
--- trunk/administrator-ro/replication-status.xml (rev 0)
+++ trunk/administrator-ro/replication-status.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 124, Lines Deleted: 0; 4310 bytes
@@ -0,0 +1,124 @@
+<?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="mysql-administrator-replication-status">
+
+ <title>Replication Status</title>
+
+ <section id="mysql-administrator-replication-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The <literal>Replication Status</literal> 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 <literal>Replication Status</literal> 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 <literal>Replication</literal>
+ tab of the <literal>Startup Variables</literal> 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/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 <literal>Hostname</literal>
+ 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 <literal>Status</literal>
+ 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 <literal>Status</literal>
+ 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/administrator-ro/restore.xml
===================================================================
--- trunk/administrator-ro/restore.xml (rev 0)
+++ trunk/administrator-ro/restore.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 169, Lines Deleted: 0; 5670 bytes
@@ -0,0 +1,169 @@
+<?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="mysql-administrator-restore">
+
+ <title>Restore</title>
+
+ <section id="mysql-administrator-restore-introduction">
+
+ <title>Introduction</title>
+
+ <para>
+ The <literal>Restore</literal> 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>
+ <literal>File to restore</literal>: 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>
+ <literal>Target Schema</literal>: You can choose the
+ <literal>Original Schema</literal> option to have all tables
+ restored into their original databases. You can also choose
+ the <literal>New Schema …</literal> 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>
+ <literal>Backup Type</literal>: At the moment, the only
+ available option is <literal>SQL Files</literal>. Those are
+ backup files containing SQL statements such as those produced
+ by <literal>mysqldump</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Ignore Errors</literal>:
+ 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>
+ <literal>Create database(s) if they don't exist</literal>: If
+ a non-existent database is referenced it will automatically be
+ created if this option is checked.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>File Charset</literal>: 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 <literal>Restore
+ Content</literal> 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/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/administrator-ro/server-connections.xml
===================================================================
--- trunk/administrator-ro/server-connections.xml (rev 0)
+++ trunk/administrator-ro/server-connections.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 148, Lines Deleted: 0; 5712 bytes
@@ -0,0 +1,148 @@
+<?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="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
+ (<literal>User</literal>, <literal>Host</literal>, 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
+ <literal>Num.</literal>. Right-clicking on a username and
+ selecting <guimenu>Show User Info</guimenu> displays the
+ <literal>Full Name</literal> and the
+ <literal>Description</literal>, as specified in the <literal>User
+ Information</literal> 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 appropriate headings
+ (<literal>Num.</literal>, <literal>Full Name</literal>, or
+ <literal>Description</literal>).
+
+ <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
+ <literal>PID</literal>. 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/administrator-ro/server-information.xml
===================================================================
--- trunk/administrator-ro/server-information.xml (rev 0)
+++ trunk/administrator-ro/server-information.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 159, Lines Deleted: 0; 4373 bytes
@@ -0,0 +1,159 @@
+<?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="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>
+ <literal>User</literal>: Username used for the current
+ connection to the MySQL server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Host</literal>: The name of the machine hosting the
+ MySQL server. This is either identical to the name listed in
+ <literal>Network Name</literal>, 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>
+ <literal>Port</literal>: 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>
+ <literal>MySQL Version</literal>: The version of the MySQL
+ server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Network Name</literal>: 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>
+
+ <literal>IP</literal>: 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>
+ <literal>Version</literal>: The version of &administrator;,
+ and the version number of the MySQL client/server protocol.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Network name</literal>: The name of the host where
+ MySQL Administrator runs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>IP</literal>: The IP number of the MySQL
+ Administrator host.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Operating System</literal>: Information about the
+ operating system on which &administrator; runs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Hardware</literal>: Information about the hardware
+ on which &administrator; runs.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ </itemizedlist>
+
+</chapter>
Added: trunk/administrator-ro/server-logs.xml
===================================================================
--- trunk/administrator-ro/server-logs.xml (rev 0)
+++ trunk/administrator-ro/server-logs.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 185, Lines Deleted: 0; 6685 bytes
@@ -0,0 +1,185 @@
+<?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="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/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 <literal>Events of page
+ <replaceable>x</replaceable> /
+ <replaceable>y</replaceable></literal>) displays the major events
+ that have occurred on the current page of the log file. The right
+ box (labeled <literal>Page Content</literal>) 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 to get the initial table locks are not
+ counted as execution time. For more information about that 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/administrator-ro/service-control.xml
===================================================================
--- trunk/administrator-ro/service-control.xml (rev 0)
+++ trunk/administrator-ro/service-control.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 334, Lines Deleted: 0; 11741 bytes
@@ -0,0 +1,334 @@
+<?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="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 have
+ connected to. Currently, this is only possible if the server is
+ running on the same machine that hosts &administrator; and if that
+ service has been configured. (Future releases will be capable of
+ starting and stopping MySQL servers on remote machines.) If the
+ server runs as a stand-alone application, the Service Control
+ section will not be enabled.
+ </para>
+
+ <para>
+ The Configure Service tab is available only for MySQL servers that
+ run under Windows.
+ </para>
+
+ </section>
+
+<!-- Introduction -->
+
+ <section id="mysql-administrator-service-control-start-stop-service">
+
+ <title>Start/Stop Service</title>
+
+ <para>
+ The <literal>Start/Stop Service</literal> tab displays the status
+ of the MySQL service. This service starts and stops the MySQL
+ server. Under <literal>Service Status</literal>, 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 <literal>Log Messages</literal>, 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 NT, 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>
+
+ <remark>
+ remove refs to NT as not supported.
+ </remark>
+
+ <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>
+ <literal>Launch MySQL server automatically</literal>: If
+ checked, the Windows service starts the MySQL server
+ automatically on operating system startup.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Display Name</literal>: 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>
+ <literal>Service Description</literal>: 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>
+ <literal>Config Filename</literal>:
+
+ <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
+ (<literal>C:\<replaceable>windows installation
+ directory</replaceable>\my.ini</literal>). <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>
+ <literal>Section Name</literal>:
+
+ <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>
+ <literal>Support for InnoDB</literal>: 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 greyed 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>
+ <literal>Support for BDB</literal>: 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 greyed 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>
+ <literal>Named Pipes</literal>: On operating systems of
+ the Windows NT family, including Windows NT, 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>
+ <literal>Debug Information (slow)</literal>: 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 greyed
+ out. See <xref linkend="server-options"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Path to Binary</literal>: 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/administrator-ro/startup-variables.xml
===================================================================
--- trunk/administrator-ro/startup-variables.xml (rev 0)
+++ trunk/administrator-ro/startup-variables.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 361, Lines Deleted: 0; 14581 bytes
@@ -0,0 +1,361 @@
+<?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="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
+ <literal>my.ini</literal>, and it is located in the Windows
+ installation directory (for example,
+ <literal>C:\WinNT\my.ini</literal>). Note that it can
+ alternatively be stored in <literal>C:\</literal>, in which case
+ it is named <literal>my.cnf</literal>. Also note that there can be
+ more than one option file. On operating systems other than
+ Windows, the option file is called <literal>my.cnf</literal>,
+ 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/administrator-ro/tray-monitor.xml
===================================================================
--- trunk/administrator-ro/tray-monitor.xml (rev 0)
+++ trunk/administrator-ro/tray-monitor.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 122, Lines Deleted: 0; 4405 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 % fixedchars.entities SYSTEM "../common/fixedchars.ent">
+ %fixedchars.entities;
+ <!ENTITY % gui-common.entities SYSTEM "../gui-common/gui-common.ent">
+ %gui-common.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
+ <literal>MySQLSystemTrayMonitor.exe</literal> 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/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>
+ <literal>Shutdown Instance:</literal> this will begin the
+ shutdown operation on the selected running service.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start Instance:</literal> this will start a currently
+ stopped server instance.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Configure Instance:</literal> 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>
+ <literal>Monitoring Options:</literal> currently the
+ <literal>Monitoring Options</literal> submenu has one available
+ option: <literal>Ignore Instance State</literal>.
+ <literal>Ignore Instance State</literal> 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 <literal>Manage MySQL Instances</literal> option of the
+ <literal>Actions</literal> 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 <literal>Monitor Options</literal> menu has two options, which
+ affect the general behavior of the &tray_monitor;. <literal>Display
+ CPU Load</literal> determines whether the CPU usage is displayed on
+ the right of the &tray_monitor;. <literal>Launch Monitor after Login
+ </literal>
+
+ <remark>
+ [MH] APPLICATION CAPITALIZATION ERROR
+ </remark>
+
+ sets the &tray_monitor;to launch when you log into Windows.
+ </para>
+
+</appendix>
Added: trunk/administrator-ro/user-administration.xml
===================================================================
--- trunk/administrator-ro/user-administration.xml (rev 0)
+++ trunk/administrator-ro/user-administration.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 491, Lines Deleted: 0; 17818 bytes
@@ -0,0 +1,491 @@
+<?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="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/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>
+ <literal>Add a new User</literal>: 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 <literal>MySQL User</literal> 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>
+ <literal>Add Host from which the User can connect</literal>:
+ 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>
+ <literal>Remove Host from which the User can
+ connect</literal>: 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>
+ <literal>Clone User</literal>: 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 <literal>MySQL User</literal> 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.
+
+ <remark>
+ [SH] Not yet implemented.
+ </remark>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Delete User</literal>: 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>
+ <literal>Refresh User List</literal>: 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/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>
+ <literal>MySQL User</literal>: 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>
+ <literal>Password</literal>: 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 highly
+ recommendable to do so.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Confirm Password</literal>: 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>
+ <literal>Full Name</literal>: As opposed to the username
+ in <literal>MySQL User</literal>, the full name may
+ contain any characters, including spaces.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Description</literal>: Additional description of
+ user.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Email</literal>: Email address of user.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Contact Information</literal>: More contact
+ information, like postal address, or messenger
+ information.
+
+ <remark>
+ [SH] Mike: messager –> messenger
+ </remark>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Icon</literal>: 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 <literal>Show Global
+ Privileges</literal> 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>
+ 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>
+
+<!-- Schema Privileges -->
+
+ <section
+id="mysql-administrator-user-administration-table-column-privileges"
+>
+
+ <title>Table Column Privileges</title>
+
+ <para>
+ This tab is available only if the <literal>Show Table/Column
+ Privileges</literal> checkbox in the
+ <link
+linkend="mysql-gui-options-administrator">Admin istrator
+ 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>
+ 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
+ -->
+
+</chapter>
Added: trunk/administrator-ro/xml-files.xml
===================================================================
--- trunk/administrator-ro/xml-files.xml (rev 0)
+++ trunk/administrator-ro/xml-files.xml 2006-12-14 21:01:23 UTC (rev 4265)
Changed blocks: 1, Lines Added: 189, Lines Deleted: 0; 7478 bytes
@@ -0,0 +1,189 @@
+<?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;
+ ]>
+ <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>
+ <literal>mysqlx-options.xml</literal>: Stores options selected
+ in the <link
+ linkend="mysql-gui-options">Options
+ dialog</link>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>mysqlx-status-variables.xml</literal>: 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>
+ <literal>mysqlx-system-variables.xml</literal>: 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>
+ <literal>mysqlx-translations-administrator.xml</literal> :
+ 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>
+ <literal>mysqlx-translations-general.xml</literal>: 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
+ <literal>mysqlx-translations-administrator.xml</literal> 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>
+ <literal>mysqlx-user-connections.xml</literal>: This file is
+ described in
+ <link linkend="mysql-gui-appendix-store-connections">How
+ &administrator; Stores Connections</link>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </appendix>
+
\ No newline at end of file
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4265 - in trunk: . administrator-ro administrator-ro/images administrator-ro/metadata | stefan | 14 Dec |
