Add Named Database Connection: Named Connections store (in a central location) authentication information associated with a user.
For information about setting up and using named connections, please see:
Note: The source and destination dataset must be set to the database name.
This specifies the machine running the PostGIS/PostgreSQL ORDBMS as either an IP address or host name. The database must have proper permissions and be set up to accept TCP/IP connections if connecting from a remote machine.
When connecting remotely, this specifies the TCP/IP port on which to connect to the ORDBMS service. The default port is 5432.
This specifies the name of the PostGIS-enabled PostgreSQL database. The database must exist in the ORDBMS.
Enter the username and password to access the database, user account, or wherever authentication is required.
If this is not set, the Table List dialog will only show choices from the Postgres search path for the current user. Selecting specific schemas here will cause tables from those schemas to be shown instead.
After you have completely specified the database connection, click the Browse button to select tables for import. A connection window appears while the system compiles a table from the database.
Once the table list appears, you can select one or more tables, and then click OK to dismiss the window. The table name(s) will appear in the table list field in the Parameter box.
This parameter exposes Format Attributes in Workbench when you create a workspace:
Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that interact with the bounding box are returned.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Select this option to remove any portions of exported features outside the area of interest.
If the table list in the PostGIS reader Reader Parameters box does not display your table, try the following:
If the table list in the PostGIS reader Reader Parameters box lists your table, but you receive an error message that the table does not exist when you run the translation, then it is likely that the PostgreSQL table has been deleted without updating the PostGIS metadata tables. Orphaned metadata may continue to exist in the PostGIS metadata tables. It is suggested that the PostGIS metadata table for the geometry columns be corrected to match only existing PostgreSQL tables.