There are 102 nodes that can be used as successor for a node with an output port of type Database Query.
A “no operation” node.
This is a Database Reader.
This is a Database Writer supporting Postgres spatial data. GT. Establishes and opens a database access connection to which the entire input table is […]
Splits a ligand-set into its components
Writer for LigandScout LSD-Files
Allows executing a Python script in a local Python environment.
This node performs a 'DISTINCT' operation on the selected column(s)
This node extracts the table dimension from a Database Query Connection
This node renames the output columns of a database connection based on the values in a reference table. The underlying database is not affected
This node lists the catalogues for a database
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.