| List: | Internals | « Previous MessageNext Message » | |
| From: | mhillyer | Date: | September 4 2004 1:13am |
| Subject: | bk commit - mysqldoc tree (MHillyer:1.2046) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of MHillyer. When MHillyer does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.2046 04/09/03 17:13:09 MHillyer@doomhammer. +13 -0 Moved a lot of common content to external files that are then included inline in the documents with SYSTEM ENTITY tags, expanded on some areas, made corrections in others. Next I'll go back to the administrator docs and get them using thses properly. Docs/query-browser/chapter-options-query-browser.xml 1.1 04/09/03 17:13:08 MHillyer@doomhammer. +100 -0 Docs/gui-common/options.png 1.1 04/09/03 17:13:08 MHillyer@doomhammer. +630 -0 Docs/gui-common/options-connection.png 1.1 04/09/03 17:13:08 MHillyer@doomhammer. +598 -0 Docs/query-browser/chapter-options-query-browser.xml 1.0 04/09/03 17:13:08 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/query-browser/chapter-options-query-browser.xml Docs/gui-common/options.png 1.0 04/09/03 17:13:08 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/gui-common/options.png Docs/gui-common/options-connection.png 1.0 04/09/03 17:13:08 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/gui-common/options-connection.png Docs/gui-common/connectionerror.png 1.1 04/09/03 17:13:07 MHillyer@doomhammer. +259 -0 Docs/gui-common/chapter-table-editor.xml 1.1 04/09/03 17:13:07 MHillyer@doomhammer. +524 -0 Docs/gui-common/chapter-options.xml 1.1 04/09/03 17:13:07 MHillyer@doomhammer. +329 -0 Docs/gui-common/appendix-troubleshooting.xml 1.1 04/09/03 17:13:07 MHillyer@doomhammer. +91 -0 Docs/administrator/chapter-options-administrator.xml 1.1 04/09/03 17:13:07 MHillyer@doomhammer. +66 -0 Docs/query-browser.xml 1.23 04/09/03 17:13:07 MHillyer@doomhammer. +33 -536 Moved more items into external files, bit of cleanup. Docs/gui-common/connectionerror.png 1.0 04/09/03 17:13:07 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/gui-common/connectionerror.png Docs/gui-common/chapter-table-editor.xml 1.0 04/09/03 17:13:07 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/gui-common/chapter-table-editor.xml Docs/gui-common/chapter-options.xml 1.0 04/09/03 17:13:07 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/gui-common/chapter-options.xml Docs/gui-common/appendix-troubleshooting.xml 1.0 04/09/03 17:13:07 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/gui-common/appendix-troubleshooting.xml Docs/gui-common/appendix-translator-notes.xml 1.3 04/09/03 17:13:07 MHillyer@doomhammer. +66 -66 Formatted Document Docs/gui-common/appendix-third-party.xml 1.3 04/09/03 17:13:07 MHillyer@doomhammer. +36 -35 Formatted document Docs/gui-common/appendix-connection-storage.xml 1.2 04/09/03 17:13:07 MHillyer@doomhammer. +36 -28 Formatted Document Docs/gui-common/appendix-common-files.xml 1.2 04/09/03 17:13:07 MHillyer@doomhammer. +32 -33 Formatted document Docs/administrator/chapter-options-administrator.xml 1.0 04/09/03 17:13:07 MHillyer@doomhammer. +0 -0 BitKeeper file C:/cygwin/home/MHillyer/mysqldoc/Docs/administrator/chapter-options-administrator.xml # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: MHillyer # Host: doomhammer. # Root: C:/cygwin/home/MHillyer/mysqldoc --- 1.22/Docs/query-browser.xml 2004-08-31 17:34:23 -06:00 +++ 1.23/Docs/query-browser.xml 2004-09-03 17:13:07 -06:00 @@ -9,6 +9,10 @@ <!ENTITY appendix-common-files SYSTEM "gui-common/appendix-common-files.xml"> <!ENTITY appendix-translator-notes SYSTEM "gui-common/appendix-translator-notes.xml"> <!ENTITY appendix-third-party SYSTEM "gui-common/appendix-third-party.xml"> +<!ENTITY appendix-troubleshooting SYSTEM "gui-common/appendix-troubleshooting.xml"> +<!ENTITY chapter-options SYSTEM "gui-common/chapter-options.xml"> +<!ENTITY chapter-options-query-browser SYSTEM "query-browser/chapter-options-query-browser.xml"> +<!ENTITY chapter-table-editor SYSTEM "gui-common/chapter-table-editor.xml"> ]> <book id="mysql-query-browser" lang="en"> @@ -353,15 +357,17 @@ <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</link> section of the + <link linkend="mysql-gui-options">Options dialog</link>. + </para> -<!--<link -linkend="">--> - - General Options section of the Options dialog - -<!--</link>--> - - . + <para> + If you have difficulties connecting, please see the + <link linkend="mysql-gui-appendix-troubleshooting-connection-errors">Troubleshooting + Connection Errors</link> section in the + <link linkend="mysql-gui-appendix-troubleshooting">Troubleshooting + Application Errors</link> appendix. </para> <para> @@ -370,12 +376,11 @@ 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. This brings up an - <literal>Options</literal> dialog window that has a - <literal>Connections</literal> section for modifying connection + connection to the MySQL server is established. The preferred method + for changing a profile is to click the <guibutton>...</guibutton> + button next to the <guilabel>Connection</guilabel> drop-down box. + This 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 @@ -827,7 +832,7 @@ <guimenu>Edit Table</guimenu> option. The &table_editor; is identical to the one used in the MySQL Administrator application. For more information on editing tables, see - <link linkend="mysql-table-editor">The MySQL Table Editor</link>. + <link linkend="gui-table-editor">The MySQL Table Editor</link>. </para> </sect2> @@ -1398,532 +1403,24 @@ <!-- END USING CHAPTER --> - <chapter id="mysql-table-editor"> - - <title> - The &table_editor; - </title> - - <sect1 id="mysql-table-editor-introduction"> - - <title> - Introduction - </title> - - <para> - The &table_editor; is a component of both the &query_browser; and - &administrator;, and allows for the visual creation and modification - of tables. - </para> - - <para> - The &table_editor; can be accessed from the &query_browser; by - right-clicking on a table within the database browser and choosing - the <guimenu>Edit Table</guimenu> option, or by right-clicking on a - database within the database browser and choosing the - <guimenu>Create New Table</guimenu> option. - </para> - - <para> - The &table_editor; can be accessed from &administrator; through the - <guimenu>Catalogs</guimenu> screen. Once you have selected a - database, right-click on a table and choose the <guimenu>Edit - Table</guimenu> option from the drop-down menu. You can also select - a table and click the <guibutton>Edit Table</guibutton> button to - access the &table_editor;. - </para> - - </sect1> - -<!-- END INTRODUCTION --> - - <sect1 id="mysql-table-editor-main-window"> - - <title> - The Main Editor Window - </title> - - <para> - The &table_editor; consists of a work space divided into three tabs, - some general information prompts, and three action buttons. - </para> - - <para> - Regardless of the tab you have active, you can always edit the table - name, the database it belongs to, and the table comment. - </para> - - <figure> - <title> - The &table_editor; - </title> - <graphic fileref="query-browser/tableeditor.png" lang="en" format="PNG"/> - </figure> - - <para> - The tabbed area is divided into three sections: - </para> - - <itemizedlist> - - <listitem><para> - <emphasis>Columns and Indices:</emphasis> Use the Columns and - Indices tab to create and modify the tables column and index - information. You can also create FOREIGN KEY relationships using - this tab. - </para></listitem> - - <listitem><para> - <emphasis>Table Options:</emphasis>Use the Table Options tab to - choose the storage engine used by the table and the table's default - character set. - </para></listitem> - - <listitem><para> - <emphasis>Advanced Options:</emphasis> Use the Advanced Options tab - to configure advanced options such as per-table storage directory, - MERGE and RAID table options, and table/row length options. - </para></listitem> - - </itemizedlist> - - <para> - Each of these sections will be discussed in further detail in the - following sections. - </para> - - </sect1> - -<!-- END MAIN WINDOW --> +<!-- INSERT THE TABLE EDITOR CHAPTER --> + &chapter-table-editor; - <sect1 id="mysql-table-editor-columns-and-indices"> + <chapter id="mysql-gui-options"> - <title> - The Columns And Indices Tab - </title> - - <para> - The <literal>Columns and Indices</literal> tab can be used to - display and edit all column and index information for your table. - Using this tab, you can add, drop, and alter columns and indexes - visually. - </para> - - <sect2 id="mysql-table-editor-columns-and-indices-column-editor"> - - <title> - The Column Editor - </title> - - <para> - You can use the column editor to change the name, datatype, default - value, and other properties of your table's columns. - </para> - - <figure> - <title> - The column editor - </title> - <graphic fileref="query-browser/columneditor.png" lang="en" format="PNG"/> - </figure> - - <para> - To change the name, datatype, default value, or comment of a - column, double-click on the value you wish to change. The value - will become editable and you can the complete your changes by - pressing the <keycap>Enter</keycap> key. - </para> - - <para> - To modify the flags on a column (<literal>UNSIGNED</literal>, - <literal>BINARY</literal>, <literal>ASCII</literal>, etc.) check - and uncheck the boxes corresponding to the flag you wish to change. - </para> - - <para> - To the left of the column name is an icon that indicates whether - the column is a member of the primary key. If the icon is a small - key, that column belongs to the primary key, otherwise a blue - diamond icon is displayed. To add or remove a column from the - primary key, you can click on the icon to toggle it. - </para> - - </sect2> - -<!-- END COLUMN EDITOR --> - - <sect2 id="mysql-table-editor-columns-and-indices-detail"> - - <title> - The Detail Area - </title> - - <para> - The detail area of the <literal>Columns and Indices</literal> tab - is divided into three tabs and is used for modifying the index, - foreign key, and miscellaneous information regarding your columns. - </para> - - <sect3 id="mysql-table-editor-columns-and-indices-detail-indices"> - - <title> - The Indices Tab - </title> - - <para> - The <literal>Indices</literal> tab holds all index information for - your table. You can add, drop, and modify indexes using the - indices tab, in combination with the column editor. - </para> - - <figure> - <title> - The index editor - </title> - <graphic fileref="query-browser/indexeditor.png" lang="en" format="PNG"/> - </figure> - - <para> - To add an index, click the <guibutton>+</guibutton> (plus) button - below the index list. You will be prompted for an index name and - the new index will be created. To drop an index, select the index - and click the <guibutton>-</guibutton> (minus) button to drop the - index from the index list. - </para> - - <para> - Use the <guilabel>Index Name</guilabel> and <guilabel>Index - Kind</guilabel> dialogues to modify the name and type - (<literal>UNIQUE</literal>, <literal>FULLTEXT</literal>, etc.) of - the index. - </para> - - <para> - To add columns to an index, either click and drag the column to - the <guilabel>Index Columns</guilabel> box or select the column - you wish to add and click the <guibutton>+</guibutton> (plus) - button to the right of the <guilabel>Index Columns</guilabel> box. - You can remove a column from the index by selecting the column and - clicking the <guibutton>-</guibutton> (minus) button to drop the - column from the index. - </para> - - <para> - To change an index to only refer to a column prefix (such as with - the CHAR and VARCHAR string datatypes), select the index column - you wish to prefix in the <guilabel>Index Columns</guilabel> box - and then click the arrow icon to the right of the <guilabel>Index - Columns</guilabel> box. Select the <guimenu>Set Index Column - Length</guimenu> option from the drop-down menu that appears. You - can set the desired prefix length in the dialogue that appears. - </para> - - </sect3> - -<!-- END INDICES TAB --> - - <sect3 id="mysql-table-editor-columns-and-indices-detail-foreign-keys"> - - <title> - The Foreign Keys Tab - </title> - - <para> - The <literal>Foreign Keys</literal> tab is divided into two - sections, one with a list of foreign keys and one with various - dialogues for foreign key settings. - </para> - - <para> - To add a foreign key, click the <guibutton>+</guibutton> (plus) - button below the foreign key list. You will be prompted to name - the new foreign key, and it will then be added to the list. - </para> - - <para> - To drop a foreign key, select the foreign key and click the - <guibutton>-</guibutton> (minus) button below the foreign key - list. The foreign key will be dropped from the foreign key list. - </para> - - <para> - You can modify the name of the foreign key, and its <literal>ON - DELETE</literal> and <literal>ON UPDATE</literal> actions using - the dialogues provided in the <guilabel>Foreign Key - Settings</guilabel> section of the tab. - </para> - - <para> - To establish a foreign key relationship, choose a table from the - <guilabel>Ref. Table</guilabel> drop-down list. The columns that - can be referenced as foreign keys will then be listed in the area - below, and you can drag a column from the column editor to the - <guilabel>Column</guilabel> section to the left of the column you - wish to reference. - </para> - - </sect3> - -<!-- END FOREIGN KEY --> - - <sect3 id="mysql-table-editor-columns-and-indices-detail-column-details"> - - <title> - The Column Details Tab - </title> - - <para> - The <literal>Column Details</literal> tab provides an interface - for setting the parameters of a column without using the table - interface of the column editor. - </para> - - <para> - All settings that are available in the - <link linkend="mysql-table-editor-columns-and-indices-column-editor">Column - Editor</link> are also available in the Column Details tab, and in - addition you can also configure the column character set and - column default collation from the Column Details tab. - </para> - - </sect3> - -<!-- END COLUMN DETAILS --> - - </sect2> - -<!-- END DETAIL AREA --> - - </sect1> - -<!-- END COLUMNS AND INDICES --> - - <sect1 id="mysql-table-editor-Table-Options"> - - <title> - The Table Options Tab - </title> - - <para> - The <literal>Table Options</literal> tab allows you to change the - storage engine and character set of your table. The potential - storage engines are listed, along with a brief summary of each - storage engine's features and strengths. - </para> - - <para> - To change the storage engine for your table, click on the radio - button next to the desired storage engine. - </para> - - <para> - To change the default character set or collation of your table, - choose a new option from the drop-down list of available character - sets. - </para> - - </sect1> - -<!-- END TABLE OPTIONS --> - - <sect1 id="mysql-table-editor-advanced-options"> - - <title> - The Advanced Options Tab - </title> - - <para> - The <literal>Advanced Options</literal> tab is used to configure - table options that would be considered outside the standard set of - options that most users designate when creating and modifying - tables. - </para> - - <para> - The <literal>Advanced Options</literal> tab is divided into several - sub-sections, each of which will be described in the upcoming - sections. - </para> - - <sect2 id="mysql-table-editor-advanced-options-various"> - - <title> - The Various Section - </title> - - <para> - The <literal>Various</literal> section of the <literal>Advanced - Options</literal> tab contains options for you to set the - <literal>PACK KEYS</literal> behavior, the table password, the - initial <literal>AUTO_INCREMENT</literal> value, and the delayed - key update behavior. - </para> - - <para> - The <literal>AUTO_INCREMENT</literal> and delayed key update - behaviors apply only to MyISAM tables. - </para> - - </sect2> - -<!-- END VARIOUS SECTION --> - - <sect2 id="mysql-table-editor-advanced-options-row-options"> - - <title> - The Row Options Section - </title> - - <para> - The <literal>Row Options</literal> section can be used to configure - options such as the row format, checksum use, and the row size - parameters needed for large tables. - </para> - - <para> - To set the row format, choose the desired row format from the - drop-down list. See - <ulink url="http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html">http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html</ulink> - for more information on the different row formats that are - available. This option only applies to MyISAM tables. - </para> - - <para> - When you expect a table to be particularly large, use the - <guilabel>Avg Row Length</guilabel>, <guilabel>Min Rows</guilabel>, - and <guilabel>Max Rows</guilabel> options to enable the MySQL - server to better accommodate your data. See - <ulink url="http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html">http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html</ulink> - for more information on how to use these options. - </para> - - </sect2> - -<!-- END ROW OPTIONS --> - - <sect2 id="mysql-table-editor-advanced-options-storage-options"> - - <title> - The Storage Options Section - </title> - - <para> - The <literal>Storage Options</literal> section is used to configure - a custom path to the table storage and data files. This option can - help improve data integrity and server performance by locating - different tables on different hard-drives. - </para> - - <para> - This option is only available for MyISAM tables and is not - available for servers running under the Windows operating system. - </para> - - </sect2> - -<!-- END STORAGE OPTIONS --> - - <sect2 id="mysql-table-editor-advanced-options-merge-options"> - - <title> - The Merge Table Options Section - </title> - - <para> - The <literal>Merge Table</literal> Options section is used to - configure MERGE tables in MyISAM. To create a MERGE table, select - MERGE as your storage engine in the - <link linkend="mysql-table-editor-Table-Options">Table Options - Tab</link> and then specify the tables you wish to MERGE in the - <guilabel>Union Tables</guilabel> dialogue. - </para> - - <para> - You can also specify the action the server should take when users - attempt to perform INSERT statements on the merge table. See - <ulink url="http://dev.mysql.com/doc/mysql/en/MERGE.html">http://dev.mysql.com/doc/mysql/en/MERGE.html - for more information on MERGE tables.</ulink> - </para> - - </sect2> - -<!-- END MERGE OPTIONS --> - - <sect2 id="mysql-table-editor-advanced-options-raid-options"> - - <title> - The Table RAID Settings Section - </title> - - <para> - The <literal>Table RAID Settings</literal> section allows you to - configure RAID support for MyISAM tables. RAID allows MyISAM tables - to grow larger than the 2GB/4GB size limit imposed by some - operating systems. - </para> - - <para> - For more information on using RAID support with MyISAM, see - <ulink url="http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html">http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html</ulink> - </para> - - </sect2> - -<!-- END RAID SECTION --> - - </sect1> - -<!-- END ADVANCED OPTIONS --> - - <sect1 id="mysql-table-editor-changes"> - - <title> - Applying Your Changes - </title> - - <para> - The changes you make with the &table_editor; are not immediately - applied but are instead queued to be applied in batches after you - have made all your edits. - </para> - - <para> - To apply the changes you have made, click the <guibutton>Apply - Changes</guibutton> button. The <literal>Confirm Table - Edit</literal> dialog will appear. - </para> - - <figure> - <title> - The Confirm Table Edit dialog - </title> - <graphic fileref="query-browser/confirmchanges.png" lang="en" format="PNG"/> - </figure> - - <para> - You can click the <guibutton>Execute</guibutton> button to confirm - the changes and have them applied, or click the - <guibutton>Cancel</guibutton> button to discard the changes. You can - also click the <guibutton>Discard Changes</guibutton> button in the - main &table_editor; window to discard all changes you have made. - </para> - - <para> - You can also copy the proposed changes to the clipboard for further - editing by highlighting the ALTER TABLE or CREATE TABLE statement, - right-clicking and choosing <guimenu>Copy</guimenu> from the - drop-down menu. - </para> - - </sect1> - -<!-- END APPLYING CHANGES --> +<!-- INSERT THE OPTIONS CHAPTER --> + &chapter-options; + <!-- INSERT THE OPTIONS CHAPTER QUERY BROWSER ENDING --> + &chapter-options-query-browser; </chapter> -<!-- END TABLE EDITOR --> +<!-- END OPTIONS CHAPTER --> + +<!-- INSERT THE TROUBLESHOOTING APPENDIX --> + &appendix-troubleshooting; -<!-- INSERT THE CONNECTION STORAGE APPENDIX --> + <!-- INSERT THE CONNECTION STORAGE APPENDIX --> &appendix-connection-storage; <!-- INSERT THE COMMON FILES APPENDIX --> @@ -1953,7 +1450,7 @@ <listitem><para> <literal>mysqlx_dbm_datatypes.xml</literal>: Stores a list of the available MySQL datatypes for use with auto-completion and with the - <link linkend="mysql-table-editor">&table_editor;</link> + <link linkend="gui-table-editor">&table_editor;</link> </para></listitem> <listitem><para> --- New file --- +++ Docs/administrator/chapter-options-administrator.xml 04/09/03 17:13:07 <sect1 id="gui-options-administrator"> <title> Administrator </title> <para> <remark> [PD] It's kind of weird that the "General Options" section in this dialog doesn't occur first...? [SH] I agree, but I am not the programmer :-) </remark> The <literal>Administrator</literal> section allows you to specify what &administrator; will display in the <link linkend="mysql-administrator-user-administration">User Administration</link> section: <itemizedlist> <listitem><para> <literal>Show Global Privileges</literal>: If checked, the <link linkend="mysql-administrator-user-administration-global-pr ivileges">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 <link linkend="privilege-system">The MySQL Access Privilege System</link> for details. If unchecked, the <link linkend="mysql-administrator-user-administration-global-pr ivileges">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-col umn-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> </para> </sect1> <!-- Administrator --> </chapter> <!-- END OPTIONS CHAPTER --> --- 1.1/Docs/gui-common/appendix-common-files.xml 2004-08-31 15:44:58 -06:00 +++ 1.2/Docs/gui-common/appendix-common-files.xml 2004-09-03 17:13:07 -06:00 @@ -1,38 +1,37 @@ <appendix id="mysql-gui-appendix-xml-files"> - <title> - XML Files Common to the MySQL GUI Applications - </title> - - <para> - XML Files Common to all MySQL GUI applications are stored in - <literal>C:\Documents and - Settings\<replaceable>UserName</replaceable>\Application - Data\MySQL</literal> directory on Windows, where - <replaceable>UserName</replaceable> is the name of the current - Windows user. On Linux, the files are stored in the - <literal>~/.mysqlgui</literal> directory. - - <itemizedlist> - - <listitem><para> - <literal>mysqlx_common_options.xml</literal>: Stores options - selected in the <link -linkend="mysql-gui-starting-options">Options - dialog</link>. - </para></listitem> - - <listitem><para> - <literal>mysqlx_user_connections.xml</literal>: This file is - described in - <link + <title> + XML Files Common to the MySQL GUI Applications + </title> + + <para> + XML Files Common to all MySQL GUI applications are stored in + <literal>C:\Documents and + Settings\<replaceable>UserName</replaceable>\Application + Data\MySQL</literal> directory on Windows, where + <replaceable>UserName</replaceable> is the name of the current Windows + user. On Linux, the files are stored in the + <literal>~/.mysqlgui</literal> directory. + + <itemizedlist> + + <listitem><para> + <literal>mysqlx_common_options.xml</literal>: Stores options + selected in the <link +linkend="mysql-gui-options">Options + dialog</link>. + </para></listitem> + + <listitem><para> + <literal>mysqlx_user_connections.xml</literal>: This file is + described in + <link linkend="mysql-gui-appendix-store-connections">How - Connections are Stored</link>. - </para></listitem> + Connections are Stored</link>. + </para></listitem> - </itemizedlist> - </para> + </itemizedlist> + </para> - </appendix> - -<!-- END COMMON XML FILES --> \ No newline at end of file +</appendix> +<!-- END COMMON XML FILES --> --- 1.1/Docs/gui-common/appendix-connection-storage.xml 2004-08-31 15:44:58 -06:00 +++ 1.2/Docs/gui-common/appendix-connection-storage.xml 2004-09-03 17:13:07 -06:00 @@ -1,13 +1,18 @@ <appendix id="mysql-gui-appendix-store-connections"> - <title> - How Connections Are Stored - </title> - - <para> - Connection profiles are stored in <literal>C:\Documents and Settings\<replaceable>UserName</replaceable>\Application Data\MySQL</literal> directory on Windows, where <replaceable>UserName</replaceable> is the name of the current Windows user. On Linux, the files are stored in the <literal>~/.mysqlgui</literal> directory. The settings are stored in a file called - <literal>mysqlx_user_connections.xml</literal>. The contents of that - file look like this: + <title> + How Connections Are Stored + </title> + + <para> + Connection profiles are stored in <literal>C:\Documents and + Settings\<replaceable>UserName</replaceable>\Application + Data\MySQL</literal> directory on Windows, where + <replaceable>UserName</replaceable> is the name of the current Windows + user. On Linux, the files are stored in the + <literal>~/.mysqlgui</literal> directory. The settings are stored in a + file called <literal>mysqlx_user_connections.xml</literal>. The + contents of that file look like this: <programlisting> @@ -30,25 +35,28 @@ </user_connection> ... </programlisting> - You can edit the file manually, but take care not to invalidate the - XML. When applying changes by editing and saving the file, those - changes will show up the next time you open the - <link - -linkend="mysql-gui-starting-options-connections">Connections</link> section of the - <link - linkend="mysql-gui-starting-options">Options - Dialog</link>. You do not need to restart your application for the - changes to take effect. - </para> - - <para> - As a database administrator, you may also edit the file according to - your preferences, and then copy it to any other machine running the MySQL GUI tools. This makes it easy to have identical - connection profiles on all machines, without having to set up those - profiles individually. All XML configuration files for the MySQL GUI Tools are cross-platform compatible and can be transferred between Windows and Linux machines. - </para> - </appendix> + You can edit the file manually, but take care not to invalidate the + XML. When applying changes by editing and saving the file, those + changes will show up the next time you open the + <link + +linkend="mysql-gui-options-connections">Connections</link> + section of the <link + linkend="mysql-gui-options">Options + Dialog</link>. You do not need to restart your application for the + changes to take effect. + </para> + + <para> + As a database administrator, you may also edit the file according to + your preferences, and then copy it to any other machine running the + MySQL GUI tools. This makes it easy to have identical connection + profiles on all machines, without having to set up those profiles + individually. All XML configuration files for the MySQL GUI Tools are + cross-platform compatible and can be transferred between Windows and + Linux machines. + </para> -<!-- END CONNECTION STORAGE --> \ No newline at end of file +</appendix> +<!-- END CONNECTION STORAGE --> --- 1.2/Docs/gui-common/appendix-third-party.xml 2004-08-31 17:34:23 -06:00 +++ 1.3/Docs/gui-common/appendix-third-party.xml 2004-09-03 17:13:07 -06:00 @@ -1,51 +1,52 @@ - <appendix id="mysql-gui-appendix-third-party-software"> +<appendix id="mysql-gui-appendix-third-party-software"> + + <title> + Third-party Software Used by the MySQL Gui Tools + </title> + + <para> + The MySQL GUI tools incorporate PCRE and PNG support through the use + of third-party libraries. + </para> + + <sect1 id="mysql-gui-appendix-third-party-software-pcre"> <title> - Third-party Software Used by the MySQL Gui Tools + PCRE Library </title> <para> - The MySQL GUI tools incorporate PCRE and PNG support through the use of third-party libraries. - </para> - - <sect1 id="mysql-gui-appendix-third-party-software-pcre"> - - <title> - PCRE Library - </title> - - <para> - Regular expression support is provided by the PCRE library package, - which is open source software, written by Philip Hazel, and - copyright by the University of Cambridge, England. The source for - the PCRE library can be found at: - <ulink + Regular expression support is provided by the PCRE library package, + which is open source software, written by Philip Hazel, and copyright + by the University of Cambridge, England. The source for the PCRE + library can be found at: + <ulink url="ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/">ftp:/ - /ftp.csx.cam.ac.uk/pub/software/programming/pcre/</ulink>. - </para> + /ftp.csx.cam.ac.uk/pub/software/programming/pcre/</ulink>. + </para> - </sect1> + </sect1> <!-- PCRE LIBRARY --> - <sect1 id="mysql-gui-appendix-third-party-software-png"> + <sect1 id="mysql-gui-appendix-third-party-software-png"> - <title> - PNG Support - </title> - - <para> - PNG support for the Windows version is provided by the TPNGImage - component which is open source software, written and copyright by - Gustavo Daud. The source for the TPNGImage can be found at: - <ulink url="http://pngdelphi.sourceforge.net"> http://pngdelphi.sourceforge.net </ulink>. - </para> + <title> + PNG Support + </title> + + <para> + PNG support for the Windows version is provided by the TPNGImage + component which is open source software, written and copyright by + Gustavo Daud. The source for the TPNGImage can be found at: + <ulink url="http://pngdelphi.sourceforge.net"> + http://pngdelphi.sourceforge.net </ulink>. + </para> - </sect1> + </sect1> <!-- PNG SUPPORT --> - </appendix> - -<!-- THIRD-PARTY SOFTWARE USED BY GUI TOOLS --> \ No newline at end of file +</appendix> +<!-- THIRD-PARTY SOFTWARE USED BY GUI TOOLS --> --- 1.2/Docs/gui-common/appendix-translator-notes.xml 2004-08-31 17:34:23 -06:00 +++ 1.3/Docs/gui-common/appendix-translator-notes.xml 2004-09-03 17:13:07 -06:00 @@ -1,69 +1,69 @@ <appendix id="mysql-administrator-appendix-notes-for-translators"> - <title> - Notes for Translators - </title> - - <para> - You may find that the MySQL GUI tools and/or their documentation are not available in your prefered - language. If you would like to translate the software, or its - documentation, or participate in that translation, <emphasis>please - contact the MySQL documentation team before starting your - translation!</emphasis> - </para> - - <para> - The MySQL documentation team's address is - <email>docs@stripped</email>. In your mail, please state what you - would like to translate (the tools, their documentation, or even the whole MySQL reference manual if you dare), and - give some information regarding your background: - - <itemizedlist> - - <listitem><para> - What is your name? - </para></listitem> - - <listitem><para> - In which country and city are you located? - </para></listitem> - - <listitem><para> - How long have you used MySQL? - </para></listitem> - - <listitem><para> - Have you done other translations? - </para></listitem> - - <listitem><para> - Will you work alone, or with a group of translators? - </para></listitem> - - <listitem><para> - What's your timetable regarding the translation? - </para></listitem> - - <listitem><para> - What is your motivation for translating? - </para></listitem> - - </itemizedlist> - - We will get back to you as soon as possible. - </para> - - <para> - The format used for both software and documentation is - <emphasis>DocBook XML</emphasis>. From that base format, all other - available formats (HTML, CHM, PDF, etc.) are being generated. It - would be a pity if you started translating, say, the HTML version of - this documentation, because we will not be able to use it in that - format. Also, you might find that someone else has already done (or is in the process of doing) that - translation. So, once again, please contact the MySQL documentation - team first! - </para> + <title> + Notes for Translators + </title> + + <para> + You may find that the MySQL GUI tools and/or their documentation are + not available in your prefered language. If you would like to + translate the software, or its documentation, or participate in that + translation, <emphasis>please contact the MySQL documentation team + before starting your translation!</emphasis> + </para> + + <para> + The MySQL documentation team's address is + <email>docs@stripped</email>. In your mail, please state what you + would like to translate (the tools, their documentation, or even the + whole MySQL reference manual if you dare), and give some information + regarding your background: + + <itemizedlist> + + <listitem><para> + What is your name? + </para></listitem> + + <listitem><para> + In which country and city are you located? + </para></listitem> + + <listitem><para> + How long have you used MySQL? + </para></listitem> + + <listitem><para> + Have you done other translations? + </para></listitem> + + <listitem><para> + Will you work alone, or with a group of translators? + </para></listitem> + + <listitem><para> + What's your timetable regarding the translation? + </para></listitem> + + <listitem><para> + What is your motivation for translating? + </para></listitem> + + </itemizedlist> + + We will get back to you as soon as possible. + </para> + + <para> + The format used for both software and documentation is + <emphasis>DocBook XML</emphasis>. From that base format, all other + available formats (HTML, CHM, PDF, etc.) are being generated. It would + be a pity if you started translating, say, the HTML version of this + documentation, because we will not be able to use it in that format. + Also, you might find that someone else has already done (or is in the + process of doing) that translation. So, once again, please contact the + MySQL documentation team first! + </para> - </appendix> - -<!-- Notes for Translators --> \ No newline at end of file +</appendix> +<!-- Notes for Translators --> --- New file --- +++ Docs/gui-common/appendix-troubleshooting.xml 04/09/03 17:13:07 <appendix id="mysql-gui-appendix-troubleshooting"> <title> Troubleshooting Application Errors </title> <para></para> <sect1 id="mysql-gui-appendix-troubleshooting-connection-errors"> <title> Troubleshooting Connection Errors </title> <para> If an error occurs when you select a connection profile and attempt to establish a connection to the MySQL server named in the profile, a window containing error information will be displayed (see figure). </para> <figure> <title> Error message dialog </title> <graphic fileref="gui-common/connectionerror.png" format="PNG" lang="en" /> </figure> <para> Normally, this means either that the credentials specified in the profile are wrong (wrong username, wrong password), or that you do not have privileges to connect to the MySQL server from the client machine. You can find more information about the error in the <ulink url="http://dev.mysql.com/doc/mysql/en/Access_denied.html">Causes of <literal>Access denied</literal> Errors</ulink> section of the reference manual. </para> <para> However, another cause of connection failure is that there might be a network problem that prevents you from reaching the machine where the MySQL server is running. For this reason, the error dialog provides a <guibutton>PING</guibutton> button. Clicking this button will send an ICMP PING request to the MySQL server host machine. If the host machine is available over the network, you will see something like this: <programlisting> Reply from 127.0.0.1: Time=0ms TTL=128 Reply from 127.0.0.1: Time=1ms TTL=128 </programlisting> This would indicate that the machine is reachable, and that the cause of connection failure is not a network problem. </para> </sect1> <!-- TROUBLESHOOTING CONNECTION ERRORS --> <sect1 id="mysql-gui-appendix-troubleshooting-display-problems"> <title> Troubleshooting Display Problems </title> <para> If, under Windows, the controls in the windows look somehow displaced, select <guimenu>Start</guimenu>, <guimenu>Control Panel</guimenu>, <guimenu>Display</guimenu>. Select the <guilabel>Settings</guilabel> tab and click the <guibutton>Advanced...</guibutton> button. Change your DPI settings to <literal>Normal (96 DPI)</literal>. </para> <para> If, under Linux, messages and captions appear very big, your display resolution is probably set too high. Use <literal>gnome-font-properties</literal> to change your default font to a smaller value or go to <literal>Details</literal> and set your resolution to <literal>72</literal> or some other more appropriate value. </para> </sect1> <!-- TROUBLESHOOTING DISPLAY PROBLEMS --> </appendix> <!-- END TROUBLESHOOTING APPENDIX --> --- New file --- +++ Docs/gui-common/chapter-options.xml 04/09/03 17:13:07 <title> Options Dialog </title> <sect1 id="mysql-gui-options-introduction"> <title> Introduction </title> <para> The <literal>Options</literal> dialog allows you to configure connection profiles, general program settings, and more. You can open the <literal>Options</literal> dialog window using one of the following methods: <itemizedlist> <listitem><para> In the connection dialog window, click the <guibutton>...</guibutton> button. </para></listitem> <listitem><para> In the main application window select <guimenu>Options ...</guimenu> from the <guimenu>Tools</guimenu> menu. </para></listitem> </itemizedlist> <figure> <title> Options dialog </title> <graphic fileref="gui-common/options.png" format="PNG" lang="en" /> </figure> In the sidebar of that dialog, you can select the section you wish to configure. There are three action buttons in the lower right corner of the window: <itemizedlist> <listitem><para> <guibutton>Apply Changes</guibutton> applies and saves changes. </para></listitem> <listitem><para> <guibutton>Discard Changes</guibutton> discards any changes you have made. </para></listitem> <listitem><para> <guibutton>Close</guibutton> closes the <literal>Options</literal> dialog window. If you have not applied or discarded your changes, you will be prompted to do so. </para></listitem> </itemizedlist> </para> </sect1> <!-- END INTRODUCTION --> <sect1 id="mysql-gui-options-general-options"> <title> General Options </title> <para> The <literal>General Options</literal> section allows you to specify a number of settings that are valid for all graphical MySQL applications. At the time of writing, &administrator; and &query_browser; are the only programs in the MySQL GUI suite, but other programs will follow soon.</para> <itemizedlist> <listitem><para> <literal>Store Window Positions</literal>: When an application is started the next time, its recent window positions will be reused. </para></listitem> <listitem><para> <literal>Show Tip of Day</literal>: If checked, a pop-up window with the tip of the day appears at program startup. </para></listitem> <listitem><para> <literal>Store Passwords</literal>: If checked, passwords are stored in the user's connection profile. In this case, you can select the password storage method: </para> <para> <literal>Plaintext</literal> means they are stored without encryption; this can be insecure. <literal>Obscured</literal> means they are encrypted using a weak algorithm. This encryption method, however, is operating system independent. Selecting <literal>OS Specific</literal> will use the default encryption method provided by your operating system. The default option is <literal>Plaintext</literal>. </para></listitem> <listitem><para> <literal>Language</literal>: Select the interface language. The default is <literal>English</literal>. </para></listitem> <listitem><para> <literal>Default Font</literal>: The font used for all aplication text.</para></listitem> <listitem><para> <literal>Data Font</literal>: The font used for all query and table data displayed. </para></listitem> <listitem><para> <literal>Code Font</literal>: The font used for all queries entered by the user.. </para></listitem> <listitem><para> <literal>Ignorelist</literal>: Whenever you check the <literal>Do Not Show This Message Again</literal> option on error and message prompts, they are added to this list. If you would like a particular message to be shown again, click the <guibutton>Remove</guibutton> button after selecting the message from the list.</para></listitem> </itemizedlist> <para>You may change the font and font size of any of the application fonts by clicking the <guibutton>Choose ...</guibutton> button to the right of the font. </para> </sect1> <!-- END GENERAL OPTIONS --> <sect1 id="mysql-gui-options-connections"> <title> Connections </title> <para> The <literal>Connections</literal> section allows you to create, edit, and delete connection profiles. The center box displays a list of currently available profiles, together with a history of connections that were made without being stored in a profile. You can collapse or expand both the <literal>Connections</literal> and <literal>History</literal> trees by double-clicking them. </para> <para> Connections are automatically added to the <literal>History</literal> tree whenever you establish a connection to a MySQL server without using one of the profiles stored under the <literal>Connections</literal> tree. They do not appear in the drop-down box of the <literal>Connection</literal> dialog, but you can use any of them by manually typing their name into the <literal>Connection</literal> box of the <literal>Connection</literal> dialog. </para> <figure> <title> Options dialog: Connections </title> <graphic fileref="gui-common/options-connection.png" format="PNG" lang="en" /> </figure> <para> To edit an existing connection profile, click on its name and change the values that appear in the <literal>Connection Parameters</literal> and <literal>Advanced Parameters</literal> tabs, then click on the <guibutton>Apply Changes</guibutton> button to save your changes. </para> <para> When you select a connection profile from either the <literal>Connections</literal> or <literal>History</literal> trees, the <literal>Connection Parameters</literal> tab displays the following fields: <itemizedlist> <listitem><para> <literal>Connection</literal>: The connection profile label. This is the name by which you refer to the profile and that appears in the <literal>Connection</literal> drop-down box of the Connection dialog. It may contain any characters, including spaces. Choose distinctive names so that you can easily tell which profiles they refer to. The names can help you distinguish connections to different MySQL servers, or connections as different MySQL users to a given server.</para></listitem> <listitem><para> <literal>Username</literal>: The username used to connect to the MySQL server. </para></listitem> <listitem><para> <literal>Password</literal>: The password used to connect to the MySQL server. Note that passwords are not stored in the connection profile, unless you specify otherwise in the <link linkend="mysql-gui-options-general-options">General Options section</link>. </para></listitem> <listitem><para> <literal>Hostname</literal>: The name of the host machine where the MySQL server runs, or its IP address. </para></listitem> <listitem><para> <literal>Port</literal>: The TCP/IP port that the MySQL server listens to on the host machine. </para></listitem> <listitem><para> <literal>Type</literal>: Specifies the protocol used to connect to the database server. The default protocol is <literal>MySQL</literal> (which uses the native MySQL protocol). The other protocols listed are not currently available. </para></listitem> <listitem><para> <literal>Schema</literal>: The default database for a connection when using the &query_browser;. </para></listitem> <listitem><para> <literal>Notes</literal>: You can use this field to enter comments or additional information describing the connection profile. </para></listitem> </itemizedlist> </para> <para> <emphasis>Note that the <literal>Advanced Parameters</literal> tab may not be available in some of the first releases of MySQL Administrator. If that is the case in the version you are using, you can still set those parameters in the Connection dialog. Use the <guibutton>Details ...</guibutton> button of that dialog to display the <literal>Advanced Connection Options</literal>.</emphasis> </para> <para> When you select a connection profile from either the <literal>Connections</literal> or <literal>History</literal> list, the <literal>Advanced Parameters</literal> tab displays the following checkboxes: <itemizedlist> <listitem><para> <literal>Use compressed protocol</literal>: If checked, the communication between the application and the MySQL server will be compressed, which may increase transfer rates. This corresponds to starting a MySQL command-line tool with the <literal>--compress</literal> option. </para></listitem> <listitem><para> <literal>Return number of found rows, not number of affected rows</literal>: By default, MySQL returns the number of rows changed by the last <literal>UPDATE</literal>, deleted by the last <literal>DELETE</literal> or inserted by the last <literal>INSERT</literal> statement. When this option is checked, the server returns the number of rows matched by the <literal>WHERE</literal> statement for <literal>UPDATE</literal> statements. </para></listitem> <listitem><para> <literal>Ignore spaces after function names, make them reserved words</literal>: Normally, any refereence to a function name in an SQL statement must be followed immediately by anopening parenthesis. If this option is checked, spaces may appear between the function name and the parenthesis, like this: <programlisting> COUNT (*) </programlisting> Enabling this option has the effect that function names become reserved words. This option corresponds to starting a MySQL command-line tool with the <literal>--ignore-spaces</literal> option. </para></listitem> <listitem><para> <literal>Allow interactive_timeout seconds of inactivity before disconnect</literal>: Normally, the connection is closed by the MySQL server after a certain period of inactivity on the client side. This period can be set with the <literal>interactive_timeout</literal> variable. If checked, the server will not close the connection unless the period of inactivity exceeds the value set by <literal>interactive_timeout</literal>. This corresponds to starting a MySQL command-line tool with the <literal>--connect-timeout=<replaceable>seconds</replaceable> </literal> option. </para></listitem> <listitem><para> <literal>Enable LOAD DATA LOCAL handling</literal>: By default, the <literal>LOCAL</literal> option of the <literal>LOAD DATA</literal> statement is disabled for security reasons. Enabling this option will allow to load data from the local machine (the machine where the client GUI application is running). This option corresponds to starting a MySQL command-line tool with the <literal>--local-infile=1</literal> option. (Note that this option is ineffective unless the MySQL server allows <literal>LOCAL</literal> handling.) </para></listitem> </itemizedlist> </para> </sect1> <!-- END CONNECTIONS --> <sect1 id="mysql-gui-options-editors"> <title>Editors</title> <para>The <literal>Editors</literal> section is used to configure options specific to the different editors available within the MySQL GUI Suite. At the time of writing this is limited to the <link linkend="gui-table-editor">&table_editor;</link>.</para> <itemizedlist> <listitem><para><literal>Show SQL command before applying changes</literal> toggles whether the &table_editor; will show you the <literal>ALTER TABLE</literal> statement it is about to execute for confirmation when you click <guibutton>Apply Changes</guibutton>.</para></listitem> <listitem><para><literal>All columns Not Null per default</literal> determines whether the &table_editor; will designate columns as being <literal>NOT NULL</literal> by default when creating new columns.</para></listitem> <listitem><para><literal>All integer columns unsigned per default</literal> sets whether integer columns are declared <literal>UNSIGNED</literal> by default when creating new columns.</para></listitem> <listitem><para><literal>PK Naming</literal> dictates the format that should be used to name <literal>PRIMARY KEY</literal> columns that are automatically generated. the <replaceable>%tablename%</replaceable> portion will be replaced with the name of the appropriate table.</para></listitem> <listitem><para><literal>Index Naming</literal> sets the name automatically generated for new indexes. The <replaceable>%nr%</replaceable> string will be replaced with an automatically incrementing number.</para></listitem> <listitem><para><literal>FK Naming</literal> configures the name used when creating new foreign keys.</para></listitem> <listitem><para><literal>PK Datatype</literal> is the datatype used when creating a <literal>PRIMARY KEY</literal> column.</para></listitem> <listitem><para><literal>Def. Datatype</literal> is the default datatype assigned to all new columns that are not part of a <literal>PRIMARY KEY</literal>.</para></listitem> </itemizedlist> </sect1> <!-- END EDITORS --> --- New file --- +++ Docs/gui-common/chapter-table-editor.xml 04/09/03 17:13:07 <chapter id="gui-table-editor"> <title> The &table_editor; </title> <sect1 id="gui-table-editor-introduction"> <title> Introduction </title> <para> The &table_editor; is a component of both the &query_browser; and &administrator;, and allows for the visual creation and modification of tables. </para> <para> The &table_editor; can be accessed from the &query_browser; by right-clicking on a table within the database browser and choosing the <guimenu>Edit Table</guimenu> option, or by right-clicking on a database within the database browser and choosing the <guimenu>Create New Table</guimenu> option. </para> <para> The &table_editor; can be accessed from &administrator; through the <guimenu>Catalogs</guimenu> screen. Once you have selected a database, right-click on a table and choose the <guimenu>Edit Table</guimenu> option from the drop-down menu. You can also select a table and click the <guibutton>Edit Table</guibutton> button to access the &table_editor;. </para> </sect1> <!-- END INTRODUCTION --> <sect1 id="gui-table-editor-main-window"> <title> The Main Editor Window </title> <para> The &table_editor; consists of a work space divided into three tabs, some general information prompts, and three action buttons. </para> <para> Regardless of the tab you have active, you can always edit the table name, the database it belongs to, and the table comment. </para> <figure> <title> The &table_editor; </title> <graphic fileref="query-browser/tableeditor.png" lang="en" format="PNG"/> </figure> <para> The tabbed area is divided into three sections: </para> <itemizedlist> <listitem><para> <emphasis>Columns and Indices:</emphasis> Use the Columns and Indices tab to create and modify the tables column and index information. You can also create FOREIGN KEY relationships using this tab. </para></listitem> <listitem><para> <emphasis>Table Options:</emphasis>Use the Table Options tab to choose the storage engine used by the table and the table's default character set. </para></listitem> <listitem><para> <emphasis>Advanced Options:</emphasis> Use the Advanced Options tab to configure advanced options such as per-table storage directory, MERGE and RAID table options, and table/row length options. </para></listitem> </itemizedlist> <para> Each of these sections will be discussed in further detail in the following sections. </para> </sect1> <!-- END MAIN WINDOW --> <sect1 id="gui-table-editor-columns-and-indices"> <title> The Columns And Indices Tab </title> <para> The <literal>Columns and Indices</literal> tab can be used to display and edit all column and index information for your table. Using this tab, you can add, drop, and alter columns and indexes visually. </para> <sect2 id="gui-table-editor-columns-and-indices-column-editor"> <title> The Column Editor </title> <para> You can use the column editor to change the name, datatype, default value, and other properties of your table's columns. </para> <figure> <title> The column editor </title> <graphic fileref="query-browser/columneditor.png" lang="en" format="PNG"/> </figure> <para> To change the name, datatype, default value, or comment of a column, double-click on the value you wish to change. The value will become editable and you can the complete your changes by pressing the <keycap>Enter</keycap> key. </para> <para> To modify the flags on a column (<literal>UNSIGNED</literal>, <literal>BINARY</literal>, <literal>ASCII</literal>, etc.) check and uncheck the boxes corresponding to the flag you wish to change. </para> <para> To the left of the column name is an icon that indicates whether the column is a member of the primary key. If the icon is a small key, that column belongs to the primary key, otherwise a blue diamond icon is displayed. To add or remove a column from the primary key, you can click on the icon to toggle it. </para> </sect2> <!-- END COLUMN EDITOR --> <sect2 id="gui-table-editor-columns-and-indices-detail"> <title> The Detail Area </title> <para> The detail area of the <literal>Columns and Indices</literal> tab is divided into three tabs and is used for modifying the index, foreign key, and miscellaneous information regarding your columns. </para> <sect3 id="gui-table-editor-columns-and-indices-detail-indices"> <title> The Indices Tab </title> <para> The <literal>Indices</literal> tab holds all index information for your table. You can add, drop, and modify indexes using the indices tab, in combination with the column editor. </para> <figure> <title> The index editor </title> <graphic fileref="query-browser/indexeditor.png" lang="en" format="PNG"/> </figure> <para> To add an index, click the <guibutton>+</guibutton> (plus) button below the index list. You will be prompted for an index name and the new index will be created. To drop an index, select the index and click the <guibutton>-</guibutton> (minus) button to drop the index from the index list. </para> <para> Use the <guilabel>Index Name</guilabel> and <guilabel>Index Kind</guilabel> dialogues to modify the name and type (<literal>UNIQUE</literal>, <literal>FULLTEXT</literal>, etc.) of the index. </para> <para> To add columns to an index, either click and drag the column to the <guilabel>Index Columns</guilabel> box or select the column you wish to add and click the <guibutton>+</guibutton> (plus) button to the right of the <guilabel>Index Columns</guilabel> box. You can remove a column from the index by selecting the column and clicking the <guibutton>-</guibutton> (minus) button to drop the column from the index. </para> <para> To change an index to only refer to a column prefix (such as with the CHAR and VARCHAR string datatypes), select the index column you wish to prefix in the <guilabel>Index Columns</guilabel> box and then click the arrow icon to the right of the <guilabel>Index Columns</guilabel> box. Select the <guimenu>Set Index Column Length</guimenu> option from the drop-down menu that appears. You can set the desired prefix length in the dialogue that appears. </para> </sect3> <!-- END INDICES TAB --> <sect3 id="gui-table-editor-columns-and-indices-detail-foreign-keys"> <title> The Foreign Keys Tab </title> <para> The <literal>Foreign Keys</literal> tab is divided into two sections, one with a list of foreign keys and one with various dialogues for foreign key settings. </para> <para> To add a foreign key, click the <guibutton>+</guibutton> (plus) button below the foreign key list. You will be prompted to name the new foreign key, and it will then be added to the list. </para> <para> To drop a foreign key, select the foreign key and click the <guibutton>-</guibutton> (minus) button below the foreign key list. The foreign key will be dropped from the foreign key list. </para> <para> You can modify the name of the foreign key, and its <literal>ON DELETE</literal> and <literal>ON UPDATE</literal> actions using the dialogues provided in the <guilabel>Foreign Key Settings</guilabel> section of the tab. </para> <para> To establish a foreign key relationship, choose a table from the <guilabel>Ref. Table</guilabel> drop-down list. The columns that can be referenced as foreign keys will then be listed in the area below, and you can drag a column from the column editor to the <guilabel>Column</guilabel> section to the left of the column you wish to reference. </para> </sect3> <!-- END FOREIGN KEY --> <sect3 id="gui-table-editor-columns-and-indices-detail-column-details"> <title> The Column Details Tab </title> <para> The <literal>Column Details</literal> tab provides an interface for setting the parameters of a column without using the table interface of the column editor. </para> <para> All settings that are available in the <link linkend="gui-table-editor-columns-and-indices-column-editor">Column Editor</link> are also available in the Column Details tab, and in addition you can also configure the column character set and column default collation from the Column Details tab. </para> </sect3> <!-- END COLUMN DETAILS --> </sect2> <!-- END DETAIL AREA --> </sect1> <!-- END COLUMNS AND INDICES --> <sect1 id="gui-table-editor-Table-Options"> <title> The Table Options Tab </title> <para> The <literal>Table Options</literal> tab allows you to change the storage engine and character set of your table. The potential storage engines are listed, along with a brief summary of each storage engine's features and strengths. </para> <para> To change the storage engine for your table, click on the radio button next to the desired storage engine. </para> <para> To change the default character set or collation of your table, choose a new option from the drop-down list of available character sets. </para> </sect1> <!-- END TABLE OPTIONS --> <sect1 id="gui-table-editor-advanced-options"> <title> The Advanced Options Tab </title> <para> The <literal>Advanced Options</literal> tab is used to configure table options that would be considered outside the standard set of options that most users designate when creating and modifying tables. </para> <para> The <literal>Advanced Options</literal> tab is divided into several sub-sections, each of which will be described in the upcoming sections. </para> <sect2 id="gui-table-editor-advanced-options-various"> <title> The Various Section </title> <para> The <literal>Various</literal> section of the <literal>Advanced Options</literal> tab contains options for you to set the <literal>PACK KEYS</literal> behavior, the table password, the initial <literal>AUTO_INCREMENT</literal> value, and the delayed key update behavior. </para> <para> The <literal>AUTO_INCREMENT</literal> and delayed key update behaviors apply only to MyISAM tables. </para> </sect2> <!-- END VARIOUS SECTION --> <sect2 id="gui-table-editor-advanced-options-row-options"> <title> The Row Options Section </title> <para> The <literal>Row Options</literal> section can be used to configure options such as the row format, checksum use, and the row size parameters needed for large tables. </para> <para> To set the row format, choose the desired row format from the drop-down list. See <ulink url="http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html">http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html</ulink> for more information on the different row formats that are available. This option only applies to MyISAM tables. </para> <para> When you expect a table to be particularly large, use the <guilabel>Avg Row Length</guilabel>, <guilabel>Min Rows</guilabel>, and <guilabel>Max Rows</guilabel> options to enable the MySQL server to better accommodate your data. See <ulink url="http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html">http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html</ulink> for more information on how to use these options. </para> </sect2> <!-- END ROW OPTIONS --> <sect2 id="gui-table-editor-advanced-options-storage-options"> <title> The Storage Options Section </title> <para> The <literal>Storage Options</literal> section is used to configure a custom path to the table storage and data files. This option can help improve data integrity and server performance by locating different tables on different hard-drives. </para> <para> This option is only available for MyISAM tables and is not available for servers running under the Windows operating system. </para> </sect2> <!-- END STORAGE OPTIONS --> <sect2 id="gui-table-editor-advanced-options-merge-options"> <title> The Merge Table Options Section </title> <para> The <literal>Merge Table</literal> Options section is used to configure MERGE tables in MyISAM. To create a MERGE table, select MERGE as your storage engine in the <link linkend="gui-table-editor-Table-Options">Table Options Tab</link> and then specify the tables you wish to MERGE in the <guilabel>Union Tables</guilabel> dialogue. </para> <para> You can also specify the action the server should take when users attempt to perform INSERT statements on the merge table. See <ulink url="http://dev.mysql.com/doc/mysql/en/MERGE.html">http://dev.mysql.com/doc/mysql/en/MERGE.html for more information on MERGE tables.</ulink> </para> </sect2> <!-- END MERGE OPTIONS --> <sect2 id="gui-table-editor-advanced-options-raid-options"> <title> The Table RAID Settings Section </title> <para> The <literal>Table RAID Settings</literal> section allows you to configure RAID support for MyISAM tables. RAID allows MyISAM tables to grow larger than the 2GB/4GB size limit imposed by some operating systems. </para> <para> For more information on using RAID support with MyISAM, see <ulink url="http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html">http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html</ulink> </para> </sect2> <!-- END RAID SECTION --> </sect1> <!-- END ADVANCED OPTIONS --> <sect1 id="gui-table-editor-changes"> <title> Applying Your Changes </title> <para> The changes you make with the &table_editor; are not immediately applied but are instead queued to be applied in batches after you have made all your edits. </para> <para> To apply the changes you have made, click the <guibutton>Apply Changes</guibutton> button. The <literal>Confirm Table Edit</literal> dialog will appear. </para> <figure> <title> The Confirm Table Edit dialog </title> <graphic fileref="query-browser/confirmchanges.png" lang="en" format="PNG"/> </figure> <para> You can click the <guibutton>Execute</guibutton> button to confirm the changes and have them applied, or click the <guibutton>Cancel</guibutton> button to discard the changes. You can also click the <guibutton>Discard Changes</guibutton> button in the main &table_editor; window to discard all changes you have made. </para> <para> You can also copy the proposed changes to the clipboard for further editing by highlighting the ALTER TABLE or CREATE TABLE statement, right-clicking and choosing <guimenu>Copy</guimenu> from the drop-down menu. </para> </sect1> <!-- END APPLYING CHANGES --> </chapter> <!-- END TABLE EDITOR --> --- New file --- +++ Docs/gui-common/connectionerror.png 04/09/03 17:13:07 PNG ±¤©NªRJ¤w:uV4¨b²^ o®4ՉYc]½JQߨ¬7H¤rX, Qm-ªKDRy]C´®N&Hd"L֠+5 us}J®P˕&H.J$R¹\ ÿ̺σy;]J?rs߱' ¢ w ½UT(s:b±X,{?/ p&\Ρ¢BBTMµ°¦ºVP#"O)=bSÿ~58F ?¢ªk¥©'¢§5ܬ²j PM] >>y|"4ǬۀT$'eQfW¥6«5]jEµ¨5µr0H¢mZZ4µ"jdlXK#-K#ZK.uþCI9ۢ±`bDYIq±DJsÿhxGm)¹?gÿ:}¯J ֲ·þ ^[ZciZZ4]jm®±-ZZk¡¹¼C£'O =<z0aI781=ٳgLh!Sk,jE¥6-^(TNkj¢,VZӥu·[u=#$ z[uݭº nsH²x s·»n·Vף>!I¢]Q§MJڜ] ¾MY&C§܇²ÿͪ´º \¼F'Kh¥¹4&7³Y9$y7¾ÿu\¼¬m`꺵/|B{Zu=4ؿ/x(kѣGd¿ d¿d =z(x(+° ՚.ՇU_''n#DY{|mz=½½Mok6½CS; {z[]¸ml8 v£ipt ¯qHRJ7u mz-l䅼+~ix/»Ҕ7%.7|apNo=°½/N>Obݣ¹¼ ¥¯S &RþzɩTqþٹ*ª˸¥ ·xF´Dc¾JNŷVvpMx0X»`3\FhrM.¤¹¼¬lqÿ¡¸»i.ϸw¢T²:¢¼´!n r³5(w=¿¸s ·Hm ³gI] $[ ¬RI?>dT±¬d ¦TKf¤Z~+Ke_º!r±L¤ 7R©º˖t_»Q˲ل}¥tAmzAIP·8\X]]y ./utºWv ²§n'v¹fk[G»6lt 3Hڸ!pF:n+¤¢¤UR¢¦¦!w|^+-cnœ²s͛¥ ,.¬´t{})_§%oOŷ8$©tZ¬vpA»{ۏ1#oyܕ?شX^I&%m¶XV«_ʿj.ltVrH=J¸ ~¼x²iM[>lt¦|ªµev[Iv 2SVp¶~°f{~nµOsy̌ ¬# ·þ´=þ NmY D*.¡ °!7|A/ᢰ+-C»Rq=q[§|]©{wl¶~7 } q3 ([9$y1¯ eN7Ky?e3{ٷo1;[IIF§µۍ6mb6:7mނ/uN ¸=Cµ2Inڴz¥´WJr¥$`¢¬a _¬i}@/ 7h.ϳs·gnþ´= П¶cwþ´=¾ix y z¢nWҪ;Q^ߐhesqQ¨¨¢9$y=¿ۏۀa´X/XT?vh3®f£?4¶O·§|A«OzG ªtºC\ÿJV ۓ^¹,S*.¬+ YE¯p¯¸ٷE|IR¹eRUBH 5~P½V¯hvQ)sc?w '«p¯Ji'L%«Lx5 '§gQ!*FѹEO£ѹhllt./g21 ~»¼¥Q? ²&2sW433;>x¾<?3 ֲ·þ^R]<FF£Og£s4'ƭ)vt~laܚ"4 ¢UbB¯®C bBl~a~~a>¶0 b ±X,6?2 pXltFf£OcB,_bwDg¾LAo{_¬·/X,+hq'xU4W&> [ DkJ595 8wþxNm#>YI@0 f֙A*M ¨htn4 ?© Nº SJB#¯6 S h ´Ù ̸°² b d!{B}'lY !d©¤ªʂ¢z°$-J%u>'ֻϾRWF|O¾J[Ӷ. ܺFc{[' ARS ¦ ´Y:r²V¯^s_'~sÿl0K<&¬ij4Z,V 96m j2G/ ¯¾ºizl¶|G :SMM- nmqªZ%.±o' KS~g7}ȾO¸k®cãF=³|yKڞ+ O&_ m6˯oF#<3³£R¿\qy¤¹:l _¼¶IW¬ȹ½ b O®e.°k J8[Vg8_myW h%»)` F$¨| V U(¦1 9¸+TmB¼gzo *8 ?~sl@( ¨¾±f®7>ª@D_P&W¤j`Bj@'b Dx?tbHՀ'?Au2¨±ÿS"En --- New file --- +++ Docs/gui-common/options-connection.png 04/09/03 17:13:08 PNG B¡P¨q ƮS'CþACQԐ́ ]=V[ + l>@D/T D*P)-©"ݺ¥wþ zwm£T½»¶t §gncsB_¤ª+*FP©m|¡R$nk·555-RBfLߛ±hђ:q[Õ¶+m"±F$4\шmO,_¹Z$4>ܴ»¥Ej ³Zm%gx: B¡P¨¨® ´ÿ ¼+x z'27v ¡/$C B5£CP B»!nM;C Bk«Z,Z½5«NN)|[d ®¼]аR &ow8 ³] ¥Z§OO?{>7?bqþJ/.[0` °+6 X[şU7 {yؿ0cyx뭆ºN~-Lo³ ½Md R9¶.l®O :v ¾ÉH-:S!¿Ȁ«%PTʓe_(|` C H K6¡db:9uT2^:baaj¹Zz&'2˫^þߒ]e/)T1ºDmWlddD8Cz#q4µsO¥Z¶61w ¿7U¿ʤi¨ml[XX.!zE~þþ+(2"¤L( --@ihii82VY KCnˠ¾uþ?w4||wr¨£'k% ib «lO>]'?Ŕ}Xru¨F%E°qO 籶·ʩ'tºYÿ킯Bϻ8(@F ~K!y>hRkc*`ƂV* C ±®4lPþ0XXXL.n|5½7Uÿ;?ºE ¢u w3e§Ys M=Il7 U2GQ%±z7*wbbk%G ¾ªlW~¼V~0¿X¥R¥R[N!EO !K6ttS\ C8j 4{n& KIr>` 6 ¡·L½jj&|þ k{aJ[¿¬ ®Jzť¦ Ֆkm?zjKfu[y¾Aq%Od.˯r0¢¾:-ɞ={!COg!bl°07),覒 !F§<+{ C6~Rþn=znݎ¦¿?hªl?Pt$±®\¶jK ®&].et3; .][*£¼Ҭ¼٦þ¾k ҁ#'D¢L&{þ a Kk<vgi¸T;}Gн08:z8z(!C82X^p A@«2«!\mU 1b~n m07Nc¹_О0~V)[s¹ߴz°Jp(L W/¿Ш{§}i¸%z²lIV§!³C֮M!tw{F¿&<<xzC>d ݙ&X~n« gN>5 H¯.-b<Q snv¿ZD4p³T 3°U@_ N¾p_ªӸ e¸i>¿«v!&' A/2V2²2Sc#0WIa«&A//0¥t«puCaҮA²(g ´)\Mj»izrWf$u1+-%JK±R3T¨*T+LKf[±±±&ɯ?tBWÿg.5ȏGTcµZѕ@>eUCkbWuFAgUC¾f7<ٴjfU C 2: )'ydViP ®6y^'m H¹f¤¼w;B /SO ¼}B骪ª Cy¹µ·ߡ¿@n*VZ*4£4x퓧,{hª<%\ ,_}d2-KP > ªX,¶Zþ¸@k`2¡¤[ ¹ > N¸j³%fWuV´:++گl$W{ ]*²H;<Sͪn ^¨'v ºM%*KehZ7` M fT3p^fT g³قR|Ϟ=3 r¹\Zb±X¯i_^!BʄR=C &! þ! ¬Ɖibaq7nxO¹iµZfk OMMW'@L!Bʄ¸k؇ Õ!zµJ\£"£ºdvnw=ɗJHm¿µyhR>½Dd:X{¢y兝mqRbHUvab´>WnKN鏛C>|5\ 0DHP@w}h;\$4jO³IlVMz»?O6X¬4W¬¢IOF DSSS/P`¾͐¢M&cd8:.¢bs%l&J2 fH¾NU) ^A`2¡r{9ͽ ° {+C)N0䧘²=WZ7y,¡l°Ti¦ZG篗r?qm©T G t°;©6fk%*Lc²@V[cv¶ & >#qt :4 Lm$Ka¢&Z`L o B¶££Ӕﴌ&t ® !&7b 5¢SLYRSOWS ( ½z/b°'iy® 3TtL¥^ɍc T ¢Jq ¯0¾ NQ85 C±s®e)0D8B GC ۋ؟W o9[º{𱱱¥¥¥:.4tQAaC y* Ag6Jl1R'0NI)¼nK¾"¢8B GC>(¾_¿³¸yl,ח+ w)'!!¡²²rpp0Na8t *lTC*´ʩ þ;O2m x7x7Ʌw23 ¼L Y" 7 y``1 9 q¶±u-n>BE}ce&$¥~* / xʇ ț£¨¸2f:¼ oe88¦}w>HQ58D 00p 0¯m#ZɼϏᒒX,ӧOC¡6;Um 9{[%@7¦ Wb%c¢|hq !#!ªM·_S?pM2C}]CChX³B!%QH%l|(@̑N±£qi;²g"^ !#!fgg:~RG{+¸+»?;211¼T0ď² FJmSI A¤d0Y|*]b³Ns¹'.¼,C¼T¿¼@+8B GCH½o¤36eV,i¾۴@0110 50h-?°x,l®L\§s| ¹ þ!b¼@N !#!*o x³'Gx<^ C[$"f³,F _ b 2©`§\';Z 9a%R)O¥&K'&'s©& _XC7,-s 0>B m W Ic `@+P>d,¤_R &EThUX! wVEGqWA§|9y 7 ±C°¥5nG {@»³4JV=þþB.£7³!Oþct°'c! A̖00yȍ 9$\"H$w !Ɯ A SVrSJ2 033#¿'چ>ª!zm( NC$ `C=$° S4ΐ K6u )C¼ Dzk|~w綺£}}} {¢m@þ$0Avɜ╿;`ox0?¬@¨q) ¦/¢@sŽjÿ§ 4 Io'!f1a ¯<uPwIþ'©-d| 0`&!C¦ D0b(t2!@ C`NF0¡` `"1 a:LC !0L'#`P0dC0 0`&!C¦ D0b(t2!@ Cȷ?Ò n¡`EC¡¤!01 C v!01 C v!01 C v!01 C v!01Զ"##C;"##cK?9m ±e½ ¯®®866bh¾¯VN͜F{8 ΐ`P0 ؠW jOk]²©Qw;¥kJ?¨¹r¿"n;b·#5¥vQZU*<l·kNMOOG£Tg1 ¡m 2Kh¶ ¡Zxiþލ¯4p$6ceJO¹m=ZYMEa»]1:ʯW´ *¹p;+®°ی?ܯ ©~6@ µ !=& ; u3'y$ p vX¶!Bµºo6£㻜+¬6c%££ºª²f,³|q\C}f¼u%ÿT]]]¥Xe oWUr%²rΔ\¹(7f¬*z½¯_¿N=!C!$<'AC ¯?lxu@m]OΖזµ46֔ wV]lqT^.6qWeg_y> §¡v!Ԡ d´P;熃!+ʭ¬¬?ÿOM?m®*<niizPY]t=ۣfG¹¥WΊ¼Λ·6]tޛv»X]z)mƊٯþÿªqCl굌-1Ļ=AI¼§´½ªeg»ǧþþv~'O[n6y=wد *;+8*o^tw44?©¬,©w7 LNýG~¿¿7Ts1v~)µWNI8ϖ¼¡qµچ@h7C¨vؓ©W[*˭}5µܵz½££½^o}SSKW ¿|nn`|?2;럛FB¡ssþ©ht* ²ܴ\®]\ZJ=!CT`L&T0²°¼ ~ÿt(4¿¼ XZ¦VVVV¦¦<Qpu5ή®ffVWkk¢ @H%B`bH Z,}?۳Gŋg¢8Mr@)C`NFz3X0²@_%` 8(v3Qh¬r¹y¾(u8ZZpLM)C`NF:4<ѧCH2 ³Dnw|]8§Ǔgµ^)"£\z<W9_I¢ !¥` Ho#sqX^7D¨C. QzC¡<«՜&'Y K2 J0d¤7C#¯>5!Bz D» \Rc(B}¢'½¢(BƉ¾!C`NFz3`$HeW'N1+?MʋF½qrr}o@H1t2қ!FY¢ŷ·mþpXK71¾¾1!¥` HoFzE¹ `T!0L'#½b( v: X,¿2={bzE ±/¾¸qD¼(XrI)C`NF:4 ѯ33kξ¾gAD« 6' Q¼q¹VkQp\\«µr @H%t2қ!|4'k"iuCH=T¸\<{ e»qD ƈ.q%sdQ!¥`v' `X!"²n j=d6x.qu_fAp@("!R P4NZJ*B5-#SD u@D>6¤N> ¢» 7i£{I0B²`± ¡dW¥,#'N{¾b\S `!`n0j&Dt:[aµ/<@H=@C¨&BFi¿x R0 Pdr#Dy¶ kwYYÿ³o{ 0`&!C¦ D0b(t2!@ C`NF0¡` ɈCÿ'{n 00Ds¡}C·R 0X4D!zÿ` ɈuC$¼ HxA~ W»]ש}͊w,?1 !ߎÿ K~ik|tº) 05nT<0@ C(b§?-%U:"hۑy>¤}»[Q<ªq5!C0b7}Bj:$Co} ¡x!C0b·47Ć¯e$¯e t !»¥¡!wB(¾;ÿ¡dΣZ '&£IC !1(jÿ(þ!o7u(½KOC쪶ÿ¯ j ¡qtW-jÿ?¬T\|S>"i´ ±~ BZ>ɋlxw¾c(-!01 C v!01n0DiS~ոl n wYϦxºe5^³иZ5'sNi j; "&O ek!IC(þΏx ½s0DC ! 7ubsje ¡ C C¤a0b¨i $@!6f±6 R ¡v¡!4^C¼ÿ±3N_W¨v^3J`4 @ µX=0V4$SX H`P>0b7" !C0b7" !C0b7" !C0b7" !C0b7" !C0VC¤[0b(t2!@ C`NF0¡` `"1 a:LC !0L'#`P0d¤sC{{'; =µµϟ<|Ӂ+;} @ C`NF:4īWK}5wzS[Po|xG 0cy߃g ®F_{ddv=]C !0L'#ny:tip³g¨2>kl¼S 1 a:«««½½£!6wuz§½B²'«39=Fcח_þ¸°I!C¦N F[^ t¸¥eH§e¨«ÿL X 76¶P_?¾ÿС ssee>©[gSzÿaP0|» lÎ_¯XYV҉!ÿk4 n·7>883946NX,µ)*8_I77·ԩ.ӱ.o4¥ @ u oS¾qþþi9gi9=?9g=u[鍖Vwn+ZµJr ܸNBr¿,Eb ! ¤I ܑ«7(¶ZD!>hL$1P|{¾y'Ny ÿnch_@²² ´F4r¡¡Aµ0ܹc6 zN7®Վi4c£ 2XETY٤@0s))©;7 71qnM¿Q(<0ދ%¾ hxxύ'"C˙B IL<Q<q kµ0cII½0B`x/Z@·!<´²²9¼:@¨T4E¡=tȔҝ7TT4¦T.@ A E++þ Cxn·[£«Dsd³R9¢, ). +(zSRii欬®´´Τ$¡q3D q`D7͛·C¦¦T³R9,0]&"Zy¼N:ݔޙD!rFuCDn,X߭kqq{/" 'o5 W&¬!n·v® tºI. ¤ь]|¾ɴ$%22:¹n6J£u9 Cx=·{N¥¾ O«¾t=8fՆH²'|$lsb~~!`ov«udu8y²?-$''tnp¬<^wZ%1јJ7''[`!Ȇ ߦ%"¯!¼0ŋW ږ-e ·¼¼<;;{-!Vھt£XdvZ쮔!²²ºRSMgaªp»\v]O²!¼]w.»®'¼\ºQ° z¼+¿¼ẍ+(p[! %!/_zm8 0k333r¹<33S&±X¬㵵 &Ӕt*¿'« «8pXX[kV«½¢¦¦{2¤$cf¦E °r¹©©¦SÔb!r )N䓫 uΔkgo¯ ½-e!r5Ȥ `g}}}}}}5&eϾvDþ#>YR6ϩ[_¾ĉ2 ªªºAf ,%)x)ef±!g!`+a·5 /N!aþsq1®_"`G?þ#ɴlAs½6^ԗq³J=ڦ^0 g͖s± U\nqmµ¾¾VːkIN6h 3q¸F˘^¡ -|Jo!rC6?> !٭·©gς!¼0µ{up[O´Zht,¿ݱµr¦ںST6Dqd>gµ^ ´I´ أ ֱ¿FE¢UU®(+p 9¹&6ǔctº16D£ud09M©©0B!C¡χ <R e wl!¯$`GEEE.\p,¿¨¨7~d¡ ?Bg8k2sy¾§R{T«v¬¾qVWTt:QZs:xY 4aXcrJGÐnHK3 ?C 4ĊE{ΦnC¡ϩhq¥0 $ߪ ; ¼0#B133Xv5Z F?½/µWXº¬¬CC³&&¬c$R³Ŗ¬,=/p).Θn`±L=©g0 3ªb-B W|O@Eþo«©¹¹jµ:·ÿ ʽe¿xƗ_]s/l{gg¶|®§ROϥA[qhbq*2**Q(t@³st¼,=£ru ®ѱ:Kyg'aC¢p»ް²C¬¦K.d²~ «·¯8wֱ7z7o\Oϥى_dd@(¦ܶ¬{jt\®ù f¦n@~0y(j ދ%bUTT¤¦¦°v ܹS^^?½zzB0!A4m`66zER`|k8Kٮ¼¼¢]©4)<~[n67W«injeµ±9ڸ0B`x/ZɩO=Sa{}ÿ_zmy?ÿ ÿº{Ob䇇¸<^qaaKEég]ÿЬ:;G³s7¾bD£PPh|m __¹g¯tnþ0B`x/Zds$*Ŗ46ka W@o ~¼?&d}o"½A{¢´T__0U¥iw\ ¾<0`˓_CX F¹D¢;d²v¡H+iB@¨Vŕ#ٽ[¼g4>¾9!SR]ÿϺ µ$Oc¨2þÿµ¡j|¥)O¢;xԻ þ삺º 'QĊFGz{gl==J+»R睱4Z*µK¥±D#´ʢ£!!±2;§%/O§!r C`01D¨/,If4u©Aª02y-mO¿ _'ڇ/\ ¾\\f㶣¿r T{ 9RXM§N䜊+CE^Z(@=`dP5_+X٭@j9 K>Z]]]SSSAAA||ޘVvJ ¥ݯ¾±ߟ\B§&&WЃ$)©\(:-¶J$bI«H¬4Be !BJeѶwd¥]<~'_²U*Uww·DZiµt^°Yw *{]11&¨-/Oްw¯4)©L,Q-2YK¾¬U*oH[&¹¼k ( ¡jͶPὟ(0*NXʫ{%¼"¹>7c4M-z{g*kz?J±=º@jp .H¤"N$ ZJu¢¥@"/h´-Tz6Noll¼rÿ§G@ `dP5Dm]S½cU©a~zT6ަh2¦ .u¥§7¼6~Gds8'E¢6 D"B٢,T+ ¥Z¡l¨ly||bnn®J¥^ZZZ»c!`D©` &LUC,,,|³ȋk¶@§8a)(2Y+ª{jTí1CdqJYa*,ⷽÿ[·n߾}ǎB¡ieaKQº°H]X¤lvMMMÿ;w@ ¨ ¡j»>??ÿo8©H?¥ ciew]`M])K|¥i[ocUQ> `0¾ÿþ={þBaH¤+,R(>-ͯMJ:V\\l±Xl6ݻw(BL ª byyY&/άl£«90'ѿþھ>CdG)11Gw~sē'OVUU ½{> <!W§¥qe2^¯?þ?ÿ_'Q( !BA,..¶´´~Rÿ]¨8aWۢm\jouuu?Zf0*J£455q8'|R 0L:U*ZnBL چ°7nܘpy;>T¶e[½7167þcÿ3³³³ԩSR©駟X,z½~hhڵkk={ @ `d6Aw}|__@ ¬©©9z觟ÿ]"¶··wwwwwwOOOߺuf³I$ 6l¸|7n߾`D¡` &LyC8²틋sssϟ YXX¸~nw¢¢¼1Y 6¬? ( !lRwܹ}͛7¯_¿~֭eWT<?Pºi° o:SZ ( Auw;1M¸byyY xe®þtu9FN1##ݏ@ GNB ±- Ad² B0¢n0a³l¨|Tُks֔͌h4g B0¢n0a³٤Ris o \u΄{fdDyyy@ٸq£d /qB0¢n0177'Ev¦]=sĩ~y³ O±!!n®A((RTTԆ 7C<f5qCh!B0Q¨n78 n·<8 >tG1+ tBA`D¡ CO+npxy·§dCx/y ` @11 ·k% B "!¢º! toW,4E0z }C(¨_ C 8 ½tC~¦¼ B @ 2 (`/5<n{>$ϩDT) G=dQ¨*!k͈`?C!!`Dk C!`D`{]n8|¯!?~O"?!PhCº ·C6®z0¢P0 ¨ Nÿ®;_;<'C!!<¡«4<!Ȼ aD¡` &L1C¬N )0 ` &L º!^> :>ٓm§ح !BL b 2 ( 0ĺ!BL AECa0¢P0&C@ `dBL CP"Q( !`JC C`0a2 A`D¡` &L!( ( Auÿ0ÿµ`D¡`X `D¡`Q7"!!`D` @@a BQ®na @T `D¡`Q7"!¢!\} Wa?T0¢J0DC EiC/N%Q:"!¢!k~@ `D¡¨eÿg̟¢¸<E~T½yzw·6#&l*1«Iղln]k¼bMD#%* H4 *Cᔛa + +4 r1zC2ÿ#ߏ{zL.±`؟v_¾UYeµ´w ¨jw¿կաzS:z44 iþ$Gν°I;.܊J˻j®,jhw¨jߠ;¨¨ WiQn AC\hX<ª r=Ý::ǑL $d}µ_y4¯4ȅn\Gpa=¤9j¯V~~BG YI§! ½جa37 ! ºu# ¡)4""FBSnU%⢂|s¾H392좂sqiu¤¦۬јwC+ˊօ?¾(4w jc 6}¼3ºª¢¤¼¬8GʏY#¢1¥!4(.,\¿p{z¢°Һp/CO{ÿ?r )?fƔД@EAS=Ñ]:C )_gƔ¿¢¨ 4wªªUUMs[ u¤|5"SBS9¡w&¨ªj»bi4ԑuֈhLiM¡!ġªªiC6FDcJChJ ;@-Um) ¹³FDcJChJ ^<¬ &'&cNWUbRdL_gƔД^<¬췣¶9/1Wm ¿ 2 Q_§ďM:¦q> d + ־RJ_5"C --- New file --- +++ Docs/gui-common/options.png 04/09/03 17:13:08 PNG B¡P(¿l`4v>U¶$.·`'j(js=½V[/ O2w~l.s+-*lª¯SL© ¡P µ¯ |¡/R*¾PUQٔ±/Ŋc±3B@¨T¡/T tfD3¡J T%%oHJ x° 0c ³\inQfZ&z¬¹X¬¬¬c- 3s^!3zq,VQ8<¹B7eUWX¬OZZ _{#ź"R¬K=_j& ³, Y sB2Dwjs:&7 NM!¼[½! ¦kmZZkoZZg£µ֮Z;s1¶űXUªv||%~µg6¨5+ª«ıX jM©0«Vr6' tcµΦ»cs¬RRkSi©]kv] t »i©ε©RR¬<6G |L&2ܩ79 &i09 &ǪN&y¡Nz7 µ¿L<s3~z,U¯\b}~P³TmЛ:¢%x't2g &5T ©©Aؓא AdNn³<~2/*+®#3i u,Vmµzbu1o·:ÿ7zo¸96[º X¬__b¶t³<@Xl= nuō2²®þ§Β \TȌ ® z,n $݂^c @ B¡bºnº$FЊÿ7Jr¾Ht3^X OKP( |M-CLw;¹܂[S L۽S} d!C B¡P®©e5¯)g 2EmY"Mf&«A)d5h24"¢-S¨¨ Ě³2Þ:]X´1''G¯߹s'¢7 /qyaӻEM5(lZQظ¼°+o7¬¸־5)\®ᘁGt!C &a da3<zoI&½GrQ 2 S[¬ºT¨¼X 8ÿXþE2¹NOr=>\?d{⢆ y¡ N7wH qX=7n»e]( Wªe>ܞs_¶}V">_Og4~GW©T.Slg&>Wa»uG/+y¡xa]( J+)˯4¼Nþ6?--JZ}-¡:¸©?¤Y{-þ[} ªjWkþղoy°hB /d²U^CoG|<b' ³p+o>:y/_}|';#Z¢t ]C¤£txj² oªH3]¬.Li¦ӕCs}˧o_e±X###n~ 4 2|d¡vt¡uv£Yþþ9 Գg®}k » ¬®®<7þ6¡! `r¹¿m3C £K_:*;IK+)) ¥K»Ά #e8:<} ²{l¶»²}°#½£+h~Âx£K0st´¼+9w ¹ »CX&n»+lÿ sCûvK&4\mx-ÿ#þ8m·BϯG_«¬¬t{ywٳCl=9°»W9{þ&;£%{rQCH<Z «&4£Cz˯b8ÿÿ¸°_ /h끁555O<9?C¹縳!d22H6ľv Μþ>>7»¹DCl,xa zC>£ W4K6¯eoÿ sCtv Xy1ۅ&4£a5H_¯{9Ǭڳe ۏ{nmm̌vqgCɦ!v z¾jd{F»P$rv`vw`l7HHþkKϏ}5ȬCp"¸/9xvrµlqvvg}}$½'aů'U(](QxxxSS{Ά ½ ӧn¸C 4 zx?Ad¥~][S jl:-;5V.W¬¹t %r©zd¤Vb Dͽ##SS5-\¡O\½h =±P" `¨ZD$µ¤c"KU~ O¬MU_«\z¾½<þU·£! jwGx?71"¤˟.1§W(S@lA9»-6ÿ5 )1% 34nNCH˖O͍þP1T75Ｋÿ7e¼Zª©µ³»wxdlfvaummkk;{Ȇ@p 9s s<Z%4 ¤2±WJ° |Jzk?&¿3Qÿ7Dþ³}>W!7¸vxCB !/¿|´¸X ¬½џº?b(~ÿ¡5615=»ܷº¶¶¹¹tD6w #±µµ% ±HAPl~Y<NQR_/±w<+ڤ§4DU¥mCB1 !?{b±mhªþրþbɛڷ?M7ڋ¯4w< [ Ȇ»>6DD=~%4P !vr "v ?1 ±¥d6P_Op o ፃ "ج¬²¾ÿAۇ ¡bh);5lqiummcc3¹ lq²«e+¿Ӏ܁"Je)3®?LijQW¾«µIL">9»¿:%C¨!¢n]C¬!4DԱ¹¹.¸&\c©\ Ȇ) ¼; Ib+8~yr=$R7d~N¥*h G"B: PC;E %F°ªS" H·ÿ/C)J Hj`<S¡ þe·<bO{CH¯ ¥Ԇ8˹ 'ow/ CWþ²kX¡xrAz%&ÿE l§Ni4i z ·rs{ ¯CԜ<yŋq½CӞ;m:z;þ»ώ6f³½%?xDϹNj4֓'{«ªee}yy´NG u:+ E .))¤'$&iµ '2sN;o! ¾.,,³!°_³YF ·§ǣ ltx¬¡ӧOyaAAkÿڟ¡¡PþQ;]Ns_,C c«?9p65JՔ٬RRE)5Iɚ¤$Mb&.¾>8¤o2Utf_vݧc_ {[·0霿:S @6K\·' 'zL1¾ ¹ y®ģb½,qyº¹~ѽy219½ (v|úۺ-t 8C/U±ubXި̺w^ºuxYYYeeeFFFHHȡt£aB¯¿ÿm§Ly-¯¨Mÿ7sȋaa¥!!þþ¸=N*H¯u2Y]¬N¦J©.m7]#\» ¦](µHT³IW ¯ #c½ 9´bN9; ¥#` C`܈o³i!7Z)±C$33{REþ>DVޭDfÿqխ2y·w:;z=ÿ£>tVrr¥TªIMU9s!Si²j²V¡¨MWu2yHT©T_!z²_7!(7(»QXp¬ .p ¾[¬!OvđCPK\. k g a̍6m\!lb6 zy BKAI[fsW¥Ʀ۷t7ZFNJJ?j{byW&:!TZ j¥R2£VY¡ªP*3jµ eL~tdrdddEEDl NG¹C!<9 zKo r#r2('½>Cp>t8썁¡Y2!\e¡¿X,o "· µ¤¬£º¦Wh® 隇o1¶:$[_o ? I*!jUµY5Y5ªUf2£&.NR]]=<<¼²²kA¼~v y/¥=0ܡX>Ma}j}-H.ByþO J tsn 3;> "N@!6!Z!yMO9<VBsBa}Ibmyu`p]©²7ÿ±풋·>!0ľO}vҥbDrС§zȑ]HK+JP( £££'N@!/¿pM:£°¹¢V{OO8<VtRmmg TYd©.´¤g6G« O+)++»~zMMMtttuuµZ®¬¬bqLLLdd¤H$ª®®}葫&N@DQ ¤C¸s{d K-W7m2:´u»${þYJ±¶¶6???<< ÿ|¶<VZ塰 ¿ÿ`N7>>/¯\¹RUUUUU%˟}ٶ¶¶UW3e! "Xfeʌb6*ªn ;æ»#¡Ғm0 ¡~8.wvvfnv¦C ?~rm±XRZZzĉ?L&ojjjmmmmm ^^^62үH$^^^KKK <pG ($ʫ btl¹W¼`Vn/f4 / q{E d/VPP`W-[¶477sG º°°?pþkn ޞ r³y¾C°i±x&¹¸Awv·a=bV ^FE霿:Sdu+(yq2 彑?#@ca}#Z\°s 4Ant=9y² r¹§3} ;½C0ÿ8:S3¯ ,su w :#@+XaM#Awu[ >ıl ?d¹ˮ> E*C 狷c!<3 z4 b܂ rnqCp>t±´¼ X6 ~;r#ze (ºC:s!±~H¹®] jt!(_ @A(f ¾M;||pCXO403/] ٌaȰ! *@ ^;ݺ{`B.Hަ«X¯ 6K&yAE~ <wt¯p !l `,|§[ : { Cxr߆ >>FePN.{}E|p!C ³dC@ Ⱥ»¬7(¢¼+Y~g«¿ լ[\!º!(g1|\wy(! ` g-{mº´ia@®I~F6 pa·±Y梅 n^Ay86!:;LC;N@!6!Z!yMO9<V¼8C@p·;/\|(l®¨^~S38¯$D$ %¾ÿQA:;G ¿·ÿLruӆ/C{]·HW±ߟux¬!x p' ¸x2£ ±q²ªz9G`ΰH¨´dþ(;H¨x ˝wx¬!x p'P^ u$²+Ht&!Rp__h+®b'Vv^¿;§³;¿3b Jԑ߬XǤX-M. x/¡vw¬O xq8Q§x6B:'s¦8b0 #eBXa`B%Ԃ; -¶C ¨=x(rx¨ 7ewSART£WZz½Վ;vT½/¾xO~eej¥唰 J¡g± *B!0±R9 |и¨=ԡMuR]£ԵF®Ct M<9¼>ύCQþ+J|?!م}ܬ |WkSf3vV!T£B±½8?\kÿ¨/=(± G¬ÿb/$?բ¶,Oѳ_-C9{²4ts2 ?B-¡ك?2wZA°4:Þ4¦,§GND~W `cy]V;)¾)(g 0LµSmC¿Cs¿¿±'vaþWin8¾vǧ¦¦=~r|>!m:T.a^-tqnN>Cڍ =wAܻµ벊N¹´-¿era´j 7c l;Ӆc||\/$pEwe:͉gqcC4r)+8DN!N|_þ²al $[wχ{ľ0ÿ¤ÿ,ݭw0>%% >´^¯7¤ "Hº0 uº½πl·rûji鼕»ϕ b¹c{ ` £%9;~L[{ ¸0ÿ_?ÿ(յwINN.((¸ÿ~gg§ =84ms¾^ݜ}Mkg.Õs¾̇¯n8y\2 Cl½Xþ²i{h'}S x=cÿk ^ÿiþ ϼº믿Ȩ¨¨p»ӡXA]½R/!.>¥¨¤¡»9 ´µvػl;¬%¢¢ʼ»¾?7:: (+:W_ a~G^= \kycͪ-{wiǧNzT(º- 8DĤ] i<0i³;z\C##n· ¿ ¼ܘ;666]ʘþuM {h#k þ23rg\JM;þþ}'ÿn]VV j>)¨Wz¿{lU⽧$ ̿ y F z T8DȣG`_ij±>¬~(»}f 8DZTq© !hC<ºs(x«¾X Ū: bQ!z ]fJ85%J@! c8{O°ÿEg U ¢½c@A>8O±7-=oM4 ؉@lYP Ehjv* rbO[S p´! BӁC¨ÿ·s?«m]y h 4UG¿kt'tÿ±OT>£/}¦±䤆8:'Y6͆c/c5 1 4ÿvDC --- New file --- +++ Docs/query-browser/chapter-options-query-browser.xml 04/09/03 17:13:08 <sect1 id="gui-options-query-browser"> <title> The Browser Section </title> <para> The <literal>Browser</literal> section allows you to specify options that relate to the &query_browser;. The <literal>Browser</literal> section is divided into three areas: <literal>Display Options</literal>, <literal>Query Options</literal>, and <literal>Various</literal>. </para> <sect2 id="gui-options-query-browser-display-options"> <title> Display Options </title> <para> The display options affect the appearance of the &query_browser;. </para> <para> <literal>Show advanced toolbars</literal> turns on and off the display of the <link linkend="mysql-query-browser-tour-buttonbar">The Advanced Toolbar</link>. </para> <para> <literal>Hide the tab when only one tab is open</literal> determines whether or not to display a tab icon at the top of the <link linkend="mysql-query-browser-tour-resultarea">Result Area</link> if there is only one active result area. </para> <para> <literal>Toolbars use gradient background</literal> enables and disables use of gradient effects in the background of the <link linkend="mysql-query-browser-tour-querybar">Query Toolbar</link>. </para> <para> <literal>Show field overlay images for long VARCHAR, TEXT, and BLOG fields</literal> toggles on and off the BLOB management icons. </para> </sect2> <!-- END DISPLAY OPTIONS --> <sect2 id="gui-options-query-browser-query-options"> <title> Query Options </title> <para> <literal>Enforce queries to be editable by adding primary key columns to the select</literal> will add <literal>PRIMARY KEY</literal> columns to a query that does not explicitly <literal>SELECT</literal> them to ensure that the results of a query can be edited. The <literal>PRIMARY KEY</literal> columns will not be displayed in this case, but will still be stored. </para> <para> <literal>Open resultset in associated application after export</literal> will cause the associated application to be opened after choosing the <guimenu>Expost Resultset</guimenu> option from the right-click menu of the <link linkend="mysql-query-browser-tour-resultarea">Result Area</link>. </para> </sect2> <!-- END QUERY OPTIONS --> <sect2 id="gui-options-query-browser-various"> <title> Various </title> <para> <literal>Associate sql/query files with Query Browser</literal> will configure Windows to associate all .sql files with the &query_browser;. As a result, all such files will be opened with &query_browser; by default. </para> </sect2> <!-- END VARIOUS --> </sect1> <!-- END QUERY BROWSER -->
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc tree (MHillyer:1.2046) | mhillyer | 4 Sep |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.145 sec. using MySQL 5.1.14-beta-log