This is a Database Reader,Establishes and opens a database access connection to read a table from. If the optional input is connected the database connection information is taken from the port, otherwise you need to specify the connection information in the dialog. Make sure you have your vendor-specific database driver registered in the KNIME preference page (section Database Driver). By default, the sun.jdbc.odbc.JdbcOdbcDriver (Windows and Linux) is only available.

Dialog Options

Database Driver

Enter the database driver here; it is a Java class (including the package path), for example: sun.jdbc.odbc.JdbcOdbcDriver Additional driver can be registered via KNIME’s preference page (Database Driver).

Database URL

Enter the database name here, for example jdbc:odbc:database_name or jdbc:mysql://host:port/database_name.

Workflow Credentials

If checked, the credentials (user and password) are used as defined on the workflow. The credential name links to the specified user and password. Those can be replaced or edit using the ‘Workflow Credentials’ menu available in the workflow context menu.

Username

Your log-in user name for the database.

Password

Your log-in password for the database. Note, the password is de- and encrypted before handling it internally.

TimeZone

Select the TimeZone to convert the date, time or timestamp field into. The current implementation can’t represent time zones. In order to support persisting those fields into a database, the time values can be changed according to the selected time zone, which is used as the offset (including the daylight saving time) for the original values: No Correction (use UTC) is used for workflows (created before 2.8) and doesn’t apply any correction, Use local TimeZone uses the local time zone offset to correct the date field before reading or writing, and TimeZone: allows selecting the time zone to covert the date values into.

SQL Statemenet

Enter SQL statement being execute here, for example SELECT * FROM table. Additional SQL commands (create, drop, set parameter, etc.) can be arrange in front of the actual SELECT statement and are execute together line-by-line during configure and execute. Note, those additional SQL commands need to be separated by semicolon.

Run SQL query only during execute, skips configure

The SQL query is executed as it is without accessing the meta info from the database during configure, which results in an empty data table spec after configure.

Database Browser

Click Fetch Metadata to connect to the database using the entered settings and to fetch all tables and display them grouped by type in a tree view. Click on any table to retrieve all contained columns. Double-click on a table or column to insert its name into the SQL query at the current cursor position.

Flow Variable List

The list contains the flow variables that are currently available at the node input. Double clicking any of the entries will insert the respective identifier at the current cursor position (replacing the selection, if any).

Further Details

Type

PostGIS Operations