From: Date: September 4 2004 1:13am Subject: bk commit - mysqldoc tree (MHillyer:1.2046) List-Archive: http://lists.mysql.com/internals/16587 Message-Id: <0I3H00307N68O8@l-daemon> MIME-Version: 1.0 Content-Type: TEXT/PLAIN Content-Transfer-Encoding: 8BIT 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 @@ + + + + ]> @@ -353,15 +357,17 @@ Password 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 + General + Options section of the + Options dialog. + - - - General Options section of the Options dialog - - - - . + + If you have difficulties connecting, please see the + Troubleshooting + Connection Errors section in the + Troubleshooting + Application Errors appendix. @@ -370,12 +376,11 @@ select another connection profile, you can change any of its values. When you click the OK 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 - ... button next to the - Connection drop-down box. This brings up an - Options dialog window that has a - Connections section for modifying connection + connection to the MySQL server is established. The preferred method + for changing a profile is to click the ... + button next to the Connection drop-down box. + This brings up an Options dialog window that has + a Connections section for modifying connection profiles. You can find the values you can set in the Connection dialog window in the description of the Connections section of the @@ -827,7 +832,7 @@ Edit Table option. The &table_editor; is identical to the one used in the MySQL Administrator application. For more information on editing tables, see - The MySQL Table Editor. + The MySQL Table Editor. @@ -1398,532 +1403,24 @@ - - - - The &table_editor; - - - - - - Introduction - - - - The &table_editor; is a component of both the &query_browser; and - &administrator;, and allows for the visual creation and modification - of tables. - - - - The &table_editor; can be accessed from the &query_browser; by - right-clicking on a table within the database browser and choosing - the Edit Table option, or by right-clicking on a - database within the database browser and choosing the - Create New Table option. - - - - The &table_editor; can be accessed from &administrator; through the - Catalogs screen. Once you have selected a - database, right-click on a table and choose the Edit - Table option from the drop-down menu. You can also select - a table and click the Edit Table button to - access the &table_editor;. - - - - - - - - - - The Main Editor Window - - - - The &table_editor; consists of a work space divided into three tabs, - some general information prompts, and three action buttons. - - - - Regardless of the tab you have active, you can always edit the table - name, the database it belongs to, and the table comment. - - -
- - The &table_editor; - - -
- - - The tabbed area is divided into three sections: - - - - - - Columns and Indices: 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. - - - - Table Options:Use the Table Options tab to - choose the storage engine used by the table and the table's default - character set. - - - - Advanced Options: 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. - - - - - - Each of these sections will be discussed in further detail in the - following sections. - - - - - + + &chapter-table-editor; - + - - The Columns And Indices Tab - - - - The Columns and Indices 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. - - - - - - The Column Editor - - - - You can use the column editor to change the name, datatype, default - value, and other properties of your table's columns. - - -
- - The column editor - - -
- - - 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 Enter key. - - - - To modify the flags on a column (UNSIGNED, - BINARY, ASCII, etc.) check - and uncheck the boxes corresponding to the flag you wish to change. - - - - 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. - - - - - - - - - - The Detail Area - - - - The detail area of the Columns and Indices tab - is divided into three tabs and is used for modifying the index, - foreign key, and miscellaneous information regarding your columns. - - - - - - The Indices Tab - - - - The Indices 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. - - -
- - The index editor - - -
- - - To add an index, click the + (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 - (minus) button to drop the - index from the index list. - - - - Use the Index Name and Index - Kind dialogues to modify the name and type - (UNIQUE, FULLTEXT, etc.) of - the index. - - - - To add columns to an index, either click and drag the column to - the Index Columns box or select the column - you wish to add and click the + (plus) - button to the right of the Index Columns box. - You can remove a column from the index by selecting the column and - clicking the - (minus) button to drop the - column from the index. - - - - 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 Index Columns box - and then click the arrow icon to the right of the Index - Columns box. Select the Set Index Column - Length option from the drop-down menu that appears. You - can set the desired prefix length in the dialogue that appears. - - - - - - - - - - The Foreign Keys Tab - - - - The Foreign Keys tab is divided into two - sections, one with a list of foreign keys and one with various - dialogues for foreign key settings. - - - - To add a foreign key, click the + (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. - - - - To drop a foreign key, select the foreign key and click the - - (minus) button below the foreign key - list. The foreign key will be dropped from the foreign key list. - - - - You can modify the name of the foreign key, and its ON - DELETE and ON UPDATE actions using - the dialogues provided in the Foreign Key - Settings section of the tab. - - - - To establish a foreign key relationship, choose a table from the - Ref. Table 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 - Column section to the left of the column you - wish to reference. - - - - - - - - - - The Column Details Tab - - - - The Column Details tab provides an interface - for setting the parameters of a column without using the table - interface of the column editor. - - - - All settings that are available in the - Column - Editor 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. - - - - - - - - - - - - - - - - - - The Table Options Tab - - - - The Table Options 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. - - - - To change the storage engine for your table, click on the radio - button next to the desired storage engine. - - - - To change the default character set or collation of your table, - choose a new option from the drop-down list of available character - sets. - - - - - - - - - - The Advanced Options Tab - - - - The Advanced Options 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. - - - - The Advanced Options tab is divided into several - sub-sections, each of which will be described in the upcoming - sections. - - - - - - The Various Section - - - - The Various section of the Advanced - Options tab contains options for you to set the - PACK KEYS behavior, the table password, the - initial AUTO_INCREMENT value, and the delayed - key update behavior. - - - - The AUTO_INCREMENT and delayed key update - behaviors apply only to MyISAM tables. - - - - - - - - - - The Row Options Section - - - - The Row Options section can be used to configure - options such as the row format, checksum use, and the row size - parameters needed for large tables. - - - - To set the row format, choose the desired row format from the - drop-down list. See - http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html - for more information on the different row formats that are - available. This option only applies to MyISAM tables. - - - - When you expect a table to be particularly large, use the - Avg Row Length, Min Rows, - and Max Rows options to enable the MySQL - server to better accommodate your data. See - http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html - for more information on how to use these options. - - - - - - - - - - The Storage Options Section - - - - The Storage Options 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. - - - - This option is only available for MyISAM tables and is not - available for servers running under the Windows operating system. - - - - - - - - - - The Merge Table Options Section - - - - The Merge Table Options section is used to - configure MERGE tables in MyISAM. To create a MERGE table, select - MERGE as your storage engine in the - Table Options - Tab and then specify the tables you wish to MERGE in the - Union Tables dialogue. - - - - You can also specify the action the server should take when users - attempt to perform INSERT statements on the merge table. See - http://dev.mysql.com/doc/mysql/en/MERGE.html - for more information on MERGE tables. - - - - - - - - - - The Table RAID Settings Section - - - - The Table RAID Settings 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. - - - - For more information on using RAID support with MyISAM, see - http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html - - - - - - - - - - - - - - Applying Your Changes - - - - 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. - - - - To apply the changes you have made, click the Apply - Changes button. The Confirm Table - Edit dialog will appear. - - -
- - The Confirm Table Edit dialog - - -
- - - You can click the Execute button to confirm - the changes and have them applied, or click the - Cancel button to discard the changes. You can - also click the Discard Changes button in the - main &table_editor; window to discard all changes you have made. - - - - 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 Copy from the - drop-down menu. - - - - - + + &chapter-options; + + &chapter-options-query-browser; - + + + + &appendix-troubleshooting; - + &appendix-connection-storage; @@ -1953,7 +1450,7 @@ mysqlx_dbm_datatypes.xml: Stores a list of the available MySQL datatypes for use with auto-completion and with the - &table_editor; + &table_editor; --- New file --- +++ Docs/administrator/chapter-options-administrator.xml 04/09/03 17:13:07 Administrator [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 :-) The Administrator section allows you to specify what &administrator; will display in the User Administration section: Show Global Privileges: If checked, the Global Privileges tab will be visible in the User Administration 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 The MySQL Access Privilege System for details. If unchecked, the Global Privileges tab will not be visible in the User Administration section. Show Table/Column Privileges: In most situations, it is sufficient to grant either global or database privileges for users. You can hide the Table/Column Privileges tab in the User Administration section by enabling this checkbox. --- 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 @@ - - XML Files Common to the MySQL GUI Applications - - - - XML Files Common to all MySQL GUI applications are stored in - C:\Documents and - Settings\UserName\Application - Data\MySQL directory on Windows, where - UserName is the name of the current - Windows user. On Linux, the files are stored in the - ~/.mysqlgui directory. - - - - - mysqlx_common_options.xml: Stores options - selected in the Options - dialog. - - - - mysqlx_user_connections.xml: This file is - described in - + XML Files Common to the MySQL GUI Applications + + + + XML Files Common to all MySQL GUI applications are stored in + C:\Documents and + Settings\UserName\Application + Data\MySQL directory on Windows, where + UserName is the name of the current Windows + user. On Linux, the files are stored in the + ~/.mysqlgui directory. + + + + + mysqlx_common_options.xml: Stores options + selected in the Options + dialog. + + + + mysqlx_user_connections.xml: This file is + described in + How - Connections are Stored. - + Connections are Stored. + - - + + - - - \ No newline at end of file + + --- 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 @@ - - How Connections Are Stored - - - - Connection profiles are stored in C:\Documents and Settings\UserName\Application Data\MySQL directory on Windows, where UserName is the name of the current Windows user. On Linux, the files are stored in the ~/.mysqlgui directory. The settings are stored in a file called - mysqlx_user_connections.xml. The contents of that - file look like this: + + How Connections Are Stored + + + + Connection profiles are stored in C:\Documents and + Settings\UserName\Application + Data\MySQL directory on Windows, where + UserName is the name of the current Windows + user. On Linux, the files are stored in the + ~/.mysqlgui directory. The settings are stored in a + file called mysqlx_user_connections.xml. The + contents of that file look like this: @@ -30,25 +35,28 @@ </user_connection> ... - 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 - Connections section of the - Options - Dialog. You do not need to restart your application for the - changes to take effect. - - - - 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. - - + 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 + Connections + section of the Options + Dialog. You do not need to restart your application for the + changes to take effect. + + + + 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. + - \ No newline at end of file + + --- 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 @@ - + + + + Third-party Software Used by the MySQL Gui Tools + + + + The MySQL GUI tools incorporate PCRE and PNG support through the use + of third-party libraries. + + + - Third-party Software Used by the MySQL Gui Tools + PCRE Library - The MySQL GUI tools incorporate PCRE and PNG support through the use of third-party libraries. - - - - - - PCRE Library - - - - 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: - ftp:/ - /ftp.csx.cam.ac.uk/pub/software/programming/pcre/. - + /ftp.csx.cam.ac.uk/pub/software/programming/pcre/. + - + - + - - PNG Support - - - - 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: - http://pngdelphi.sourceforge.net . - + + PNG Support + + + + 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: + + http://pngdelphi.sourceforge.net . + - + - - - \ No newline at end of file + + --- 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 @@ - - Notes for Translators - - - - 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, please - contact the MySQL documentation team before starting your - translation! - - - - The MySQL documentation team's address is - docs@stripped. 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: - - - - - What is your name? - - - - In which country and city are you located? - - - - How long have you used MySQL? - - - - Have you done other translations? - - - - Will you work alone, or with a group of translators? - - - - What's your timetable regarding the translation? - - - - What is your motivation for translating? - - - - - We will get back to you as soon as possible. - - - - The format used for both software and documentation is - DocBook XML. 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! - + + Notes for Translators + + + + 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, please contact the MySQL documentation team + before starting your translation! + + + + The MySQL documentation team's address is + docs@stripped. 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: + + + + + What is your name? + + + + In which country and city are you located? + + + + How long have you used MySQL? + + + + Have you done other translations? + + + + Will you work alone, or with a group of translators? + + + + What's your timetable regarding the translation? + + + + What is your motivation for translating? + + + + + We will get back to you as soon as possible. + + + + The format used for both software and documentation is + DocBook XML. 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! + - - - \ No newline at end of file + + --- New file --- +++ Docs/gui-common/appendix-troubleshooting.xml 04/09/03 17:13:07 Troubleshooting Application Errors Troubleshooting Connection Errors 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).
Error message dialog
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 Causes of Access denied Errors section of the reference manual. 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 PING 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: Reply from 127.0.0.1: Time=0ms TTL=128 Reply from 127.0.0.1: Time=1ms TTL=128 This would indicate that the machine is reachable, and that the cause of connection failure is not a network problem. Troubleshooting Display Problems If, under Windows, the controls in the windows look somehow displaced, select Start, Control Panel, Display. Select the Settings tab and click the Advanced... button. Change your DPI settings to Normal (96 DPI). If, under Linux, messages and captions appear very big, your display resolution is probably set too high. Use gnome-font-properties to change your default font to a smaller value or go to Details and set your resolution to 72 or some other more appropriate value. --- New file --- +++ Docs/gui-common/chapter-options.xml 04/09/03 17:13:07 Options Dialog Introduction The Options dialog allows you to configure connection profiles, general program settings, and more. You can open the Options dialog window using one of the following methods: In the connection dialog window, click the ... button. In the main application window select Options ... from the Tools menu.
Options dialog
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: Apply Changes applies and saves changes. Discard Changes discards any changes you have made. Close closes the Options dialog window. If you have not applied or discarded your changes, you will be prompted to do so. General Options The General Options 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. Store Window Positions: When an application is started the next time, its recent window positions will be reused. Show Tip of Day: If checked, a pop-up window with the tip of the day appears at program startup. Store Passwords: If checked, passwords are stored in the user's connection profile. In this case, you can select the password storage method: Plaintext means they are stored without encryption; this can be insecure. Obscured means they are encrypted using a weak algorithm. This encryption method, however, is operating system independent. Selecting OS Specific will use the default encryption method provided by your operating system. The default option is Plaintext. Language: Select the interface language. The default is English. Default Font: The font used for all aplication text. Data Font: The font used for all query and table data displayed. Code Font: The font used for all queries entered by the user.. Ignorelist: Whenever you check the Do Not Show This Message Again 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 Remove button after selecting the message from the list. You may change the font and font size of any of the application fonts by clicking the Choose ... button to the right of the font. Connections The Connections 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 Connections and History trees by double-clicking them. Connections are automatically added to the History tree whenever you establish a connection to a MySQL server without using one of the profiles stored under the Connections tree. They do not appear in the drop-down box of the Connection dialog, but you can use any of them by manually typing their name into the Connection box of the Connection dialog.
Options dialog: Connections
To edit an existing connection profile, click on its name and change the values that appear in the Connection Parameters and Advanced Parameters tabs, then click on the Apply Changes button to save your changes. When you select a connection profile from either the Connections or History trees, the Connection Parameters tab displays the following fields: Connection: The connection profile label. This is the name by which you refer to the profile and that appears in the Connection 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. Username: The username used to connect to the MySQL server. Password: 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 General Options section. Hostname: The name of the host machine where the MySQL server runs, or its IP address. Port: The TCP/IP port that the MySQL server listens to on the host machine. Type: Specifies the protocol used to connect to the database server. The default protocol is MySQL (which uses the native MySQL protocol). The other protocols listed are not currently available. Schema: The default database for a connection when using the &query_browser;. Notes: You can use this field to enter comments or additional information describing the connection profile. Note that the Advanced Parameters 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 Details ... button of that dialog to display the Advanced Connection Options. When you select a connection profile from either the Connections or History list, the Advanced Parameters tab displays the following checkboxes: Use compressed protocol: 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 --compress option. Return number of found rows, not number of affected rows: By default, MySQL returns the number of rows changed by the last UPDATE, deleted by the last DELETE or inserted by the last INSERT statement. When this option is checked, the server returns the number of rows matched by the WHERE statement for UPDATE statements. Ignore spaces after function names, make them reserved words: 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: COUNT (*) Enabling this option has the effect that function names become reserved words. This option corresponds to starting a MySQL command-line tool with the --ignore-spaces option. Allow interactive_timeout seconds of inactivity before disconnect: 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 interactive_timeout variable. If checked, the server will not close the connection unless the period of inactivity exceeds the value set by interactive_timeout. This corresponds to starting a MySQL command-line tool with the --connect-timeout=seconds option. Enable LOAD DATA LOCAL handling: By default, the LOCAL option of the LOAD DATA 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 --local-infile=1 option. (Note that this option is ineffective unless the MySQL server allows LOCAL handling.) Editors The Editors 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 &table_editor;. Show SQL command before applying changes toggles whether the &table_editor; will show you the ALTER TABLE statement it is about to execute for confirmation when you click Apply Changes. All columns Not Null per default determines whether the &table_editor; will designate columns as being NOT NULL by default when creating new columns. All integer columns unsigned per default sets whether integer columns are declared UNSIGNED by default when creating new columns. PK Naming dictates the format that should be used to name PRIMARY KEY columns that are automatically generated. the %tablename% portion will be replaced with the name of the appropriate table. Index Naming sets the name automatically generated for new indexes. The %nr% string will be replaced with an automatically incrementing number. FK Naming configures the name used when creating new foreign keys. PK Datatype is the datatype used when creating a PRIMARY KEY column. Def. Datatype is the default datatype assigned to all new columns that are not part of a PRIMARY KEY. --- New file --- +++ Docs/gui-common/chapter-table-editor.xml 04/09/03 17:13:07 The &table_editor; Introduction The &table_editor; is a component of both the &query_browser; and &administrator;, and allows for the visual creation and modification of tables. The &table_editor; can be accessed from the &query_browser; by right-clicking on a table within the database browser and choosing the Edit Table option, or by right-clicking on a database within the database browser and choosing the Create New Table option. The &table_editor; can be accessed from &administrator; through the Catalogs screen. Once you have selected a database, right-click on a table and choose the Edit Table option from the drop-down menu. You can also select a table and click the Edit Table button to access the &table_editor;. The Main Editor Window The &table_editor; consists of a work space divided into three tabs, some general information prompts, and three action buttons. Regardless of the tab you have active, you can always edit the table name, the database it belongs to, and the table comment.
The &table_editor;
The tabbed area is divided into three sections: Columns and Indices: 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. Table Options:Use the Table Options tab to choose the storage engine used by the table and the table's default character set. Advanced Options: 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. Each of these sections will be discussed in further detail in the following sections. The Columns And Indices Tab The Columns and Indices 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. The Column Editor You can use the column editor to change the name, datatype, default value, and other properties of your table's columns.
The column editor
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 Enter key. To modify the flags on a column (UNSIGNED, BINARY, ASCII, etc.) check and uncheck the boxes corresponding to the flag you wish to change. 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. The Detail Area The detail area of the Columns and Indices tab is divided into three tabs and is used for modifying the index, foreign key, and miscellaneous information regarding your columns. The Indices Tab The Indices 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.
The index editor
To add an index, click the + (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 - (minus) button to drop the index from the index list. Use the Index Name and Index Kind dialogues to modify the name and type (UNIQUE, FULLTEXT, etc.) of the index. To add columns to an index, either click and drag the column to the Index Columns box or select the column you wish to add and click the + (plus) button to the right of the Index Columns box. You can remove a column from the index by selecting the column and clicking the - (minus) button to drop the column from the index. 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 Index Columns box and then click the arrow icon to the right of the Index Columns box. Select the Set Index Column Length option from the drop-down menu that appears. You can set the desired prefix length in the dialogue that appears. The Foreign Keys Tab The Foreign Keys tab is divided into two sections, one with a list of foreign keys and one with various dialogues for foreign key settings. To add a foreign key, click the + (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. To drop a foreign key, select the foreign key and click the - (minus) button below the foreign key list. The foreign key will be dropped from the foreign key list. You can modify the name of the foreign key, and its ON DELETE and ON UPDATE actions using the dialogues provided in the Foreign Key Settings section of the tab. To establish a foreign key relationship, choose a table from the Ref. Table 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 Column section to the left of the column you wish to reference. The Column Details Tab The Column Details tab provides an interface for setting the parameters of a column without using the table interface of the column editor. All settings that are available in the Column Editor 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. The Table Options Tab The Table Options 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. To change the storage engine for your table, click on the radio button next to the desired storage engine. To change the default character set or collation of your table, choose a new option from the drop-down list of available character sets. The Advanced Options Tab The Advanced Options 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. The Advanced Options tab is divided into several sub-sections, each of which will be described in the upcoming sections. The Various Section The Various section of the Advanced Options tab contains options for you to set the PACK KEYS behavior, the table password, the initial AUTO_INCREMENT value, and the delayed key update behavior. The AUTO_INCREMENT and delayed key update behaviors apply only to MyISAM tables. The Row Options Section The Row Options section can be used to configure options such as the row format, checksum use, and the row size parameters needed for large tables. To set the row format, choose the desired row format from the drop-down list. See http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html for more information on the different row formats that are available. This option only applies to MyISAM tables. When you expect a table to be particularly large, use the Avg Row Length, Min Rows, and Max Rows options to enable the MySQL server to better accommodate your data. See http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html for more information on how to use these options. The Storage Options Section The Storage Options 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. This option is only available for MyISAM tables and is not available for servers running under the Windows operating system. The Merge Table Options Section The Merge Table Options section is used to configure MERGE tables in MyISAM. To create a MERGE table, select MERGE as your storage engine in the Table Options Tab and then specify the tables you wish to MERGE in the Union Tables dialogue. You can also specify the action the server should take when users attempt to perform INSERT statements on the merge table. See http://dev.mysql.com/doc/mysql/en/MERGE.html for more information on MERGE tables. The Table RAID Settings Section The Table RAID Settings 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. For more information on using RAID support with MyISAM, see http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html Applying Your Changes 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. To apply the changes you have made, click the Apply Changes button. The Confirm Table Edit dialog will appear.
The Confirm Table Edit dialog
You can click the Execute button to confirm the changes and have them applied, or click the Cancel button to discard the changes. You can also click the Discard Changes button in the main &table_editor; window to discard all changes you have made. 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 Copy from the drop-down menu. --- New file --- +++ Docs/gui-common/connectionerror.png 04/09/03 17:13:07 PNG  NRJw:uV4b^ o4ՉYc]JQߨ7HrX, Qm-KDRy]CN&Hd"L֠+5 us}JP˕&H.J$R\ ̺σy;]J?rs߱'  wUT(s:bX,{?/p&\۝ΡBBTMVP#"O)=bS~58F ?k'5ܬj PM] >>y|"4ǬۀT$'eQfW65]jE5r0HmZZ4"jdlXK#-K#ZK.uCI9ۢ`bDYIqDJshxGm)?g:}J ֲ ^[ZciZZ4]jm-ZZkC'O=!I]QMJڜ]MY&C܇ͪ\F'Kh4&7Y9$y7¾u\m`꺵/|B{Zu=4ؿ/x(kѣGd dd=z(x(+՚.ՇU_''n#DY{|mz=Mok6CS; {z[]ml8viptqHRJ7umz-l䅼+~ix/Ҕ7%.7|apNo=/N>Obݣ  S &RzɩTqٹ*˸xFDcJNŷVvpMx0X`3\FhrM.¤lqi.ϸwT:!nr5(w=sHmgI] $[RI?>dTdTKfZ~+Ke_!rL 7R˖t_Q˲ل}tAmzAIP8\X]]y./utWv n‰'vfk[G6lt3Hڸ!pF:n+UR!w|^+-cnœs͛,.t{})_%oOŷ8$tZvpA{ۏ1#oyܕ?شX^I&%mXV_ʿj.ltVrH=J~xiM[>lt|ev[Iv 2SVp~f{~nOsy̌ #= NmYD*. !7|A/ᢰ+-CRq=q[|]{wl~7 } q3 ([9$y1eN7Ky?e3{ٷo1;[IIFۍ6mb6:7mނ/uN =C2InڴzWJr$`a_i}@/7h.ϳsgn=Пcw=ix y znWҪ;Q^ߐhesqQ9$y=ۏۀaX/XT?vh3f?4O|AOzGtC\JVۓ^,S*.+YEpٷE|IReRUBH 5~PVhvQ)sc?w'pJi'L%Lx5 'gQ!*FѹEOѹhllt./g21~Q? &2sW433;>x<΍?3 ֲ^R]0b X,6?2pXltFfOcB,_bwDgLAo{_/X,+hq'xU4W&>[ DkJ595 8wxNm#>YI@0f֙A*M htn4 ? N SJB#6 S  h Ù ̸ b d!{B}'lY  !dʂz$-J%u>'ֻϾRWF|OJ[Ӷ. ܺFc{[' ARS Y:rV^s_'~sl0K<&ij4Z,V 96m j2G/ izl|G:SMM-nmqZ%.o' KS~g7}ȾOk„cF=|yKڞ+ O&_ m6˯oF#<3R\qy:l _IWȹ b Oe.k J8[Vg8_myWh%)`F$|V U(1 9԰+TmBgzo*8 ?΀~sl@(  f7>@D_P&Wj`Bj@'b Dx?tbHՀ'?Au2S"En --- New file --- +++ Docs/gui-common/options-connection.png 04/09/03 17:13:08 PNG  BPq ƮS'CACQԐ́]=V[ + l>@D/T D*P)-"ݺw׶zwmTtgncsB_+*FPm|R$nk555-RBfLߛhђ:q[Õ+m"F$4\шmO,_Z$4>ܴEj Zm%gx: BP +x z'27v /$C B5CP B!nM;C BkZ,Z5NN)|[d ]аR &ow8] ZOO?{>7?bqJ/.[0`+6 X[şU7{yؿ0cyx뭆N~-LoMdR9.lO :vÉH-:S!Ȁ%PTʓe_(|`C H K6db:9uT2^:baajZz&'2˫^ߒ]e/)T1DmWlddD8Cz#q4sOZ61w7Uʤiml[XX.!zE~+(2"L( --@ihii82VY KCnˠu?w4||wr£'k% ib lO>]'?Ŕ}XruF%EqO 籶ʩ'tY킯Bϻ8(@F~K!y>hRkc*`ƂV* C4lP0XXXL.n|57U;?Euw3eYs M=Il7U2GQ%z7*wbbk%GlW~V~0X¥RR[N!EO!K6ttS\C8j 4{n& KIr>`6 Ljj&|k{aJ[JzťՖkm?zjKfu[yAq%Od.˯r0:-ɞ={׽!COg!bl07),覒 !F<+{ C6~Rn=znݎ¦?hl?Pt$\jK &].et3; .][*Ҭ٦k ҁ#'DL&{‡ aKk܎d ݙ΢&X~ngN>5 H.-bv!&' A/2V22Sc#0WIa&A//0tpuCaҮA(g )\MjizrWf$u1+-%JKR3T*T+LKf[&ɯ?tBWg.5ȏGTcZѕ@>eUCkbWuFAgUCf7<ٴjfUC 2: )'ydViP 6y^'m Hfw;B/SO}B骪 Cyߡ@n*VZ*44x퓧,{h<%\,_}d2-KP >  X,Z@k`2[  Nj%fWuV:++گl$W{ ]*H;<Sͪn^'v M%*KehZ7` M fT3p^fTgقR|Ϟ=3 r\ZbXi_^!BʄR=C &! !Ɖibaq7nxOiZfk OMMW'@L!Bʄk؇ Õ!zJ\"dvnw=ɗJHmyhR>Dd:X{y兝mqRbHUvab>WnKN鏛C>|5\ 0DHP@w}h;\$4jOIlVMz?O6X4WIOFDSSS/P`͐M&cd8:.bs%l&J2 fHNU) ^A`2r{9ͽ {+C)N0䧘=WZ7y,lTiZG篗r?qmT G t;6fk%*Lc@V[cv &>#qt :4 Lm$Ka&Z`Lo BӔﴌ&t  !&7b 5SLYRSOWS (z/b'iy3TtL^ɍcT Jq 0NQ85Cse)0D8B GC ۋ؟W o9[{𱱱:.4tQAaC y* Ag6Jl1R'0NI)nK"8B GC>(_yl,ח+w)'!!rpp0Na8t*lTC*ʩ ;O2mx7x7Ʌw23 LY" 7 y``19 qu-n>BE}ce&$~* /xʇ ț2f: oe88}w>HQ58D 00p0m#ZɼϏᒒX,ӧOC6;Um9{[%@7Wb%c|hq   !#!M_S?pM2C}]CChXB!%QH%l|(@̑Nqi;g"^   !#!fgg:~RG{++?;211T0ď FJmSI Ad0Y|*]bNs'.,CT@+8B GCHo36eV,i۴੔@0110 50h-?x,lL\s| !b@N  !#!*ox'Gx<^C[$"f,F _b 2`\';Z 9a%R)O&K'&'s& _XC7,-s0>BmW Ic`@+P>d,_R &EThUX!wVEGqWA|9y 7 C5nG{@4JV=B.7!Oct'c! A̖00yȍ 9$\"H$w!Ɯ A SVrSJ2 033#'چ>!zm( NC$ `C=$ S4ΐ K6u )C Dzk|~w綺}}} {m@$0Avɜ╿;`ox0?@q) /@sŽj4Io'!f1a v!ԠdP;熃!+ʭ?OM?m*5!Bz D \Rc(B}'(BƉ!C`NFz3`$HeW'N1+?MʋFqrr}o@H1t2қ!FYŷ·mpXK711!` HoFzE`T!0L'#b( v: X,2={bzE /qD(XrI)C`NF:4 ѯ33kξgAD 6'QqVkQp\\r@H%t2қ!|4'k"iuCH=T\<{eqDƈ.q%sdQ!`v' `X!"nj=d6x.qu_fAp@("!R P4NZJ*B5-#SD u@D>6N> 7i{I0B` dW,#'N{b\S `!`n0j&Dt:[a/<@H=@C&BFix R0 Pdr#DykwYYo{ 0`&!C D0b(t2!@ C`NF0` ɈC'{n  00Ds}CR 0X4D!z` ɈuC$ HxA~ W]ש}͊w,?1 !ߎ K~ik|tƒ)05nT<0@ C(b?-%U:"hۑy>}[Q"i ~BZ>ɋlxwc(-!01 C v!01n0DiS~ոl n wYϦxe5^иZ5'sNi j; "&Oek!IC(Ώxs0DC !7ubsje CCa0bi $@!6f6 R v!4^C3N_Wv^3J`4 @ X=0V4$SX H`P>0b7" !C0b7" !C0b7" !C0b7" !C0b7" !C0VC[0b(t2!@ C`NF0` `"1 a:LC !0L'#`P0dsC{{';=ϟ<|Ӂ+;} @ C`NF:4īWK}5wzS[Po|xG  0cy߃g F_{ddv=]C !0L'#ny:tipg2>klS 1 a:!6wuzB'39=Fcח_I!CN F[^ teHeLX 76P_?Сssee>[gSzaP0|lÎ_XYV҉!k4 n7>883946NX,)*8_I77ԩ.ӱ.o4@ uoSqi9gi9=?9g=u[鍖Vwn+ZJr ܸNBr,Eb ! I ܑ7(ZD!>hL$1P|{y'Ny nch_@ F4rA0ܹc6 zN7Վi4c 2XETY٤@0s));7 71qnMQ(<0ދ%hxxύ'"C˙BILYR6ϩ[_ĉ2 Af ,%)x)ef!g!`+a5/N!asq1_"`G?#ɴlAs6^ԗqJ=ڦ^0 g͖s U\nqmVːkIN6h 3qF˘^-|Jo!rC6?>!٭gς!0{up[OZht,ݱrںST6Dqd>g^Iأ ֱFEUU(+p 9&6ǔct16Dud09M0B!Cχ 9!SR]Ϻ$Oc2j|)O;xԻ삺'QĊFGz{gl==J+R睱4Z*KD#ʢ!!2;%/O!r C`01D/,If4uA02y-mO_'ڇ/\\\f㶣r T{9RXMN䜊+CE^Z(@=`dP5_+X٭@j9 K>Z]]]SSSAAA||ޘVvJݯ׷ߟ\B&&WЃ$)\(:-J$bIH4Be  !BJeѶwd]<~'_U*UwwDZit^Yw*{]11&-/Oްw4)L,Q-2YKU*oH[&k ( jͶPὟ(0*NXʫ{%">7c4M-z{g*kz?J=@jp .H"N$ ZJu@"/h-Tz6NollrÿG@ `dP5Dm]ScUa~zT6ަh2.u76~Gds8'E6 D"B٢,T+ Zlly||bnnJ^ZZZc!`D` &LUC,,,|ȋk@8a)(2Y+{jTí1CdqJYa*,ⷽ[n߾}ǎBieaKQH]XlvMMM;w@  j>??o8H? ciew]`M])K|i[ocUQ>`0={BaH+,R(>-ͯMJ:V\\lXl6ݻw(BL  byyY&/άl90'ѿھ>CdG)11Gw~sē'OVUU ½{>Te[7167c3ԩSR駟X,z~hhڵkk={ @ `d6Aw޽}|__@ 9z觟]"wwwwwwOOOߺufI$ 6l|7n߾`D` &LyC8틋sssϟYXX~nw1Y 6? ( !lRwܹ}͛7_~֭eWTtG1+ tBA`DCO+npxydCx/y ` @11 k% B "!!toW,4E0z }C(_ C 8 ޷tC~ B @2 (`/5$ϩDT) 񯆀G=dQ*!k͈`?C!!`Dk C!`D`{]n8|!?~O"?!PhC C6z0P0  N;_;<'C!!<4:>ٓmح!BL b2 ( 0ĺ!BL AECa0P0&C@ `dBL CP"Q( !`JC C`0a2 A`D` &L!( ( Au0`D`X `D`Q7"!!`D` @@a BQna@T `D`Q7"!!\} Wa?T0J0DC EiC/N%Q:"!!k~@ `Deg̟<E~޷Tyzw6#&l*1Iղln]kbMD#%*H4 *Cᔛa + +4 r1zC2#ߏ{zL.`Š؟v_UYew jwկաzS:z44 i$GνI;.܊J˻j,jhwjߠ;꡽WiQn AC\hX<r=Ý::ǑL $d}_y44ȅn\Gpa=9jV~~BG YI! جa37! u# )4""FBSnU%⢂|sH392좂sqiu۬јwC+ˊօ?(4w jc 6}38GʏY#1!4(.,\p{zҺp/CO{?r)?fƔД@EAS=Ñ]:C)_gƔ 4wUUMs[ u|5"SBS9w&jbi4ԑ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  BP(l`4v>U$.`'j(js=V[/ O2w~l.s+-*lSL P |/R*PUQٔ/Ŋc3B@T/T tfD3J T%%oHJ x 0c \inQfZ&zXc- 3s^!3zq,VQ8\?d{⢆ y N7wH qX=7ne]( We>ܞs_}V">_Og4~GWT.Slg&>WauG/+yxa]( J+)˯4N6?--JZ}-:?Y{-[} jWkղoyhB /dU^CoG|:y/_}|';#Zt ]CtxjoH3].LiӕCs}˧o_eX###n~ 4 2|dvtuvY9Գg}k <76! `rm3CK_:*;IK+))KΆ #e8:<} {l}#+h~ÂxK0st+9w CX&n+lsCûvK&4\mx-#8mBϯG_t{ywٳCl=9W9{&;%{rQCH>7DCl,xazC>W4K6eosCtv Xy1ۅ&4a5H_{9Ǭڳe ۏ{nmm̌vqgCɦ!vzjd{FP$rv`vw`l7HHkKϏ}5ȬCp"/9xvrlqvvg}}$'aů'U(](QxxxSS{Ά  ӧnC4 zx?Ad~][S jl:-;5V.Wt %rzdVb Dͽ##SS5-\O\h =P"  `ZD$c"KU~OMU_\zW!7vxCB !/|Xџ?׽󋒰b(~5615=ܷtD6w #% HAPl~Y6DD=~%4P !vr"v?1 d6P_Op oፃ "جAۇ bh);5lqiummcc3lqe+Ӏ܁"Je)3?LijQWIL">9:%C!n]C!4DԱ.&\c\ Ȇ) ;Ib+8~yr=$R7d~N*hG"B: PC;E%FS" H/C)J Hj`8o2Utf_vݧc_ {[0霿:S @6K\''zL1 yģb,qy~ѽy219 (v|úۺ-t8C/UubXި̺w^uxYYYeeeFFFHHȡtaBmLy-M7s𙈈ȋaa!!=N*Hu2Y]NJ.m7]#\¦](HTIW“#‰c 9bN9;¥#` C`܈oi!7Z)C$33{RE>DVޭDfqխ2y񖛣w:;z=>tVrrTIMU9s!SijVMWu2yHTT_!z_7!(7(QXp .p [!OvđCPK\.kg a̍6m\!lb6zy BKAI[fsWƦ۷t7ZFNJJ?j{byW&:!TZ jR2VYP*3j eL~tdrdddEEDl NGC!<9 zKor#r2('>Cp>t8썁Y2!\eX,o"Wh 隇o1:$[_o?I*!jUY5Y5Uf2&.NR]]=<Ma}j}-H.ByO J tsn 3;> "N@!6!Z!yMO9!0ľO}vҥbDrСzȑ]HK+JP( 'N@!/pM:V{OO8>/\RUUUUU%˟}ٶUW3e!"Xfeʌb6*n;æ#Ғm0 ~8.wvvfnvC ?~rmXRZZzĉ?L&ojjjmmmmm^^^62үH$^^^KKKıl ?dˮ>E*C狷c!<3 z4b܂rnqCp>t X6 ~;r#ze (C:s!~H]jt!(_ @A(f M;||pCXO403/]  ٌaȰ!*@ ^;ݺ{`B.HަX6K&yAE~>FePN.{}E|p!C dC@Ⱥ7(+Y~gլ[\!!(g1|\wy(!`g-{mia@I~F6 paY梅 n^Ay86!:;LC;N@!6!Z!yMO9ύCQ+J|?!م}ܬ |WkSf3vV!TB8?\k/=( Gb/$?բ,Oѳ_-C9{4ts2 ?B-ك?2wZA4:Þ4,GND~W `cy]V;))(g 0LSmCCs'vaWin8vÇ=~r|>!m:T.a^-tqnN>Cڍ =wAܻ벊N-eraj 7cl;Ӆc||\/$pEwe:͉gqcC4r)+8DN!N|_al$[wχ{ľ0,ݭw0>%%>^7"H0uπlrûji鼕ϕbc{ ` %9;~L[{0_?(յwINN.((~gg =84ms^ݜ}Mkg.Õṡn8y\2ClXi{h'}Sx=ck ^i ϼ믿ȨpӡXA]R/!.>9 vػl;%ʼ?7::(+:W_ a~G^=\kycͪ-{wiǧNzT(-8DĤ]i<0i;z\C##n ܘ;666]ʘuM {h#k23rg\JM;}'n]VV  j>)Wz{lU⽧$  ̿  y F zT8DȣG`_ij>~(}f 8DZTq !hC8O7-=oM4؉@lYPEhjv* rbO[S p!BӁCs?m]y h4UGkt'tOT>/}䤆8:'Y6͆c/c5 14vDC --- New file --- +++ Docs/query-browser/chapter-options-query-browser.xml 04/09/03 17:13:08 The Browser Section The Browser section allows you to specify options that relate to the &query_browser;. The Browser section is divided into three areas: Display Options, Query Options, and Various. Display Options The display options affect the appearance of the &query_browser;. Show advanced toolbars turns on and off the display of the The Advanced Toolbar. Hide the tab when only one tab is open determines whether or not to display a tab icon at the top of the Result Area if there is only one active result area. Toolbars use gradient background enables and disables use of gradient effects in the background of the Query Toolbar. Show field overlay images for long VARCHAR, TEXT, and BLOG fields toggles on and off the BLOB management icons. Query Options Enforce queries to be editable by adding primary key columns to the select will add PRIMARY KEY columns to a query that does not explicitly SELECT them to ensure that the results of a query can be edited. The PRIMARY KEY columns will not be displayed in this case, but will still be stored. Open resultset in associated application after export will cause the associated application to be opened after choosing the Expost Resultset option from the right-click menu of the Result Area. Various Associate sql/query files with Query Browser 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.