DB Query

Modifies the SQL query that defines the incoming DB Data table. The incoming SQL query is represented by the place holder #table# and will be replaced during execute thus creating a sub-query. The resulting SQL query defines the new DB Data table at the out-port.

Options

SQL Statement

SQL editor to enter a new database query based on the incoming DB Data represented by the #table# place holder.
To open code completion press <CTRL> + <SPACE>. Table and columns names are only suggested if the metadata is available e.g. shown in the Database Metadata Browser. To perform undo press <CTRL> + Z and for re-do <CTRL> + Y.
Don't remove the #table# place holder which represents the incoming SQL statement.

Database Metadata Browser

The Database Metadata Browser allows you to browse the database metadata and to select a table or view. Click the Refresh button at the bottom right to re-fetch the metadata from the database. The data is grouped by database schema and type e.g. view or table. By clicking on an entity it shows contained elements. If you click on a table or view the dialog will fetch the column names and types of the selected element. To select a table or view double click the element. To search for a particular table or view enter the name or parts of the name into the search field and click on the Magnifying Glass button or press enter.

Database Column List

The list contains the columns that are available in the incoming DB Data table. Double clicking any of the entries will insert the respective identifier at the current cursor position (replacing the selection, if any).

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).

Preview

To evaluate the SQL query click on the Evaluate button. This will trigger the execution of the query in the database and fetches the top 10 rows of the result.
Please notice that the query that is used to fetch the preview data is altered to only return the top 10 rows for efficiency usually by wrapping it into a LIMIT statement.

Views

This node has no views

Workflows

• 01.2 Database Extension and In-Spark ProcessingKNIME Hub
• 02_Database_Advanced_ExampleKNIME Hub
• 02_Database_Advanced_ExampleKNIME Hub
• 02_Database_Advanced_ExampleKNIME Hub
• 02_Database_Advanced_ExampleKNIME Hub
• Show all 212 workflows

Links

• How can we run DB QUERY node without LIMIT Clause?by SnigdhaBiswas on 2023-01-04

  forum.knime.com/p/187257

Developers