From f9e422988715b66932e025b72612ac06a7b4c065 Mon Sep 17 00:00:00 2001 From: guillaume Date: Fri, 5 Jun 2009 15:50:12 +0000 Subject: [PATCH] =?utf8?q?Documentation=20fixes,=20from=20Marek=20=C4=8Cer?= =?utf8?q?nock=C3=BD.?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit git-svn-id: svn://svn.pgadmin.org/trunk/pgadmin3@7897 a7884b65-44f6-0310-8a51-81a127f17b15 --- docs/en_US/bugreport.html | 2 ++ docs/en_US/editgrid.html | 2 +- docs/en_US/options-tab1.html | 12 ++++++------ docs/en_US/pgadmin3.hhc | 5 +++++ docs/en_US/query.html | 2 +- docs/en_US/status.html | 9 --------- 6 files changed, 15 insertions(+), 17 deletions(-) diff --git a/docs/en_US/bugreport.html b/docs/en_US/bugreport.html index 0cbf83e1c..143873116 100644 --- a/docs/en_US/bugreport.html +++ b/docs/en_US/bugreport.html @@ -32,8 +32,10 @@ mailing list, and include the following informations:

  • If possible and appropriate, include a backtrace from the crash. You may need to recompile wxWidgets and pgAdmin with the --enable-debug option to do this. +

    Please do not send an email directly to one of the programmers; they might miss it, or even be the wrong person altogether. Using the mailing list guarantees that your request isn't lost and will be answered in a timely fashion. +

    After a bug has been reported on the mailing list as being fixed, it might take one or two days until it has made it into the distribution tarballs, please be patient.

    diff --git a/docs/en_US/editgrid.html b/docs/en_US/editgrid.html index 9b89fa88e..33152f6db 100644 --- a/docs/en_US/editgrid.html +++ b/docs/en_US/editgrid.html @@ -70,7 +70,7 @@ preference is appended to the current sort order.
    • the currently selected rows in the descending order of the selected column values. If a sorting preference is already present for this data set, this sorting preference is appended to the current sort order. -
  • Remove Filter: When selected, removes all sorting preferences for +
  • Remove Sorting: When selected, removes all sorting preferences for this data set.
    • Note: If a column is already selected for sorting, it's position in the sort diff --git a/docs/en_US/options-tab1.html b/docs/en_US/options-tab1.html index 8cc3a67a6..ea3c65632 100644 --- a/docs/en_US/options-tab1.html +++ b/docs/en_US/options-tab1.html @@ -41,33 +41,33 @@ to the Slony help files, and may be configured in the same way as the PG help path. The Slony Help is used when selected from the Help menu.
      -
  • System schemas- You can suppress the display of additional schemas, +
  • System schemas - You can suppress the display of additional schemas, by declaring them a system schema. This field takes a list of comma separated strings.
     
    • -
  • Slony-I path- To enable pgAdmin III to create Slony-I replication clusters +
  • Slony-I path - To enable pgAdmin III to create Slony-I replication clusters from scratch, you need to enter the path to the Slony-I script installation directory here. If no valid scripts can be found, only joining existing clusters is possible.
     
    • -
  • PG bin path- This should be set to the path to the standard PostgreSQL pg_dump, pg_restore +
  • PG bin path - This should be set to the path to the standard PostgreSQL pg_dump, pg_restore and pg_dumpall utilities. pgAdmin will use these for backing up and restoring your PostgreSQL databases. If this path is not set, pgAdmin will attempt to find the utilities in its installation directory, the 'hint' directory set by a local PostgreSQL installation (on Windows) and in the system path.
     
    • -
  • EDB bin path- This should be set to the path to the EnterpriseDB pg_dump, pg_restore +
  • EDB bin path - This should be set to the path to the EnterpriseDB pg_dump, pg_restore and pg_dumpall utilities. pgAdmin will use these for backing up and restoring your EnterpriseDB databases. If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by EnterpriseDB.
     
    • -
  • GP bin path- This should be set to the path to the Greenplum pg_dump, pg_restore +
  • GP bin path - This should be set to the path to the Greenplum pg_dump, pg_restore and pg_dumpall utilities. pgAdmin will use these for backing up and restoring your Greenplum databases. If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by Greenplum.
     
    • -
  • Ignore server/utility version mismatches- When checked, pgAdmin will pass the '-i' option +
  • Ignore server/utility version mismatches - When checked, pgAdmin will pass the '-i' option to utilities such as pg_dump which will allow utilities from one version of the database to be used with another version. This option should be use with extreme care as it may cause errors to occur during backup or restore options. diff --git a/docs/en_US/pgadmin3.hhc b/docs/en_US/pgadmin3.hhc index b2d8199ff..698110531 100644 --- a/docs/en_US/pgadmin3.hhc +++ b/docs/en_US/pgadmin3.hhc @@ -232,6 +232,11 @@ +
  • + + + +
  • diff --git a/docs/en_US/query.html b/docs/en_US/query.html index 43bc9ef83..9b0e12a59 100644 --- a/docs/en_US/query.html +++ b/docs/en_US/query.html @@ -17,7 +17,7 @@

    The upper part of the Query Tool contains the SQL Editor where you type your commands. You may read the query from a file, or write it out to a file. When writing a file, the encoding of the file -is determined by the file suffix: if it is *.sql, a 8 byte local +is determined by the file suffix: if it is *.sql, a 8 bit local character set is used. If *.usql is selected, the file will be written in UTF-8, which enables the storage of virtually all characters used throughout the world, according to the coding rules diff --git a/docs/en_US/status.html b/docs/en_US/status.html index 6b102e8ff..9cfab9c6f 100644 --- a/docs/en_US/status.html +++ b/docs/en_US/status.html @@ -37,15 +37,6 @@ instead of by it's name, if the relation is in a different database to that being monitored.

    -The Cancel button allows cancelling the query running on a specific -backend. Terminate will shutdown the backend. Attention: Both functions should be -used carefully, as the interrupt the client's work -ungracefully. particularly, the terminate function might disturb the -function of the complete server, force it to restart its services and -thus interrupt all user connections. You should use this function only -if the server is seriously injured by a backend you can't control otherwise. -

    -

    Note: When the pg_locks view is accessed as is the case whenever this dialgue is open, PostgreSQL's internal lock manager data structures are momentarily locked, and a copy is made for the dialogue to display. This -- 2.39.5