Oracle Query Builder Helper¶
Interactive helper for exploring an Oracle database and assembling queries without deep SQL knowledge. It can discover tables, list a table's columns, suggest potential JOINs, and build/execute a basic query from natural language requirements. Outputs can be returned as plain text with JSON, or exported to HTML, XLSX, and PDF formats.
Usage¶
Use this node when you need to understand your Oracle schema and quickly assemble queries. Typical workflow: start with discover_tables to see available tables in a schema, use get_table_columns for structure, run suggest_joins to see likely relationships, then use build_query to generate and execute a basic query from a description. Choose output_format to get helper results or executed query results in text/HTML/XLSX/PDF.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to the stored Oracle credentials used by the node to authenticate. | |
| timeout | True | INT | Maximum time in seconds to wait for the service to respond before failing. | 60 |
| action | True | ENUM | Operation to perform. Options: discover_tables, get_table_columns, suggest_joins, build_query. | discover_tables |
| target_schema | True | STRING | Oracle schema name to explore. Leave empty to use the current user schema. | HR |
| table_name | True | STRING | Table name to inspect (used by get_table_columns and suggest_joins). Can be left empty for other actions. | EMPLOYEES |
| query_requirements | True | STRING | Natural language description of the data you want (used by build_query). | Find employees and their department names |
| output_format | True | ENUM | Desired output format. Options: text (plain text + JSON), html (HTML table), xlsx (Excel), pdf (PDF), all (returns exports as available). | text |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Human-readable textual result, such as table/column listings, join suggestions, or query results. | Oracle Tables in Schema: HR EMPLOYEES DEPARTMENTS LOCATIONS |
| json | STRING | JSON-serialized data payload of the operation (e.g., lists of tables/columns, suggestions, or query results). | {"suggestions": {"table": "EMPLOYEES", "suggested_joins": [{"type": "INNER", "table": "DEPARTMENTS", "schema": "HR", "on": "EMPLOYEES.DEPARTMENT_ID = DEPARTMENTS.DEPARTMENT_ID"}]}} |
| html | HTML | HTML rendition for display (populated when output_format is html or all). | Oracle Join Suggestions: EMPLOYEES... |
| xlsx | XLSX | Binary XLSX export containing the results (populated when output_format is xlsx or all). | |
| Binary PDF export containing the results (populated when output_format is pdf or all). |
Important Notes¶
- Action-specific requirements: table_name is required for get_table_columns and suggest_joins. query_requirements is used by build_query.
- Schema handling: target_schema can be left empty to use the current user schema.
- Execution behavior: build_query generates a basic heuristic query and executes it; the executed SQL is returned in the JSON under built_query.
- Output formats: text returns text and JSON. html/xlsx/pdf return only that export plus JSON. all includes exports via the service and may include text where applicable.
- Credentials: Ensure the credentials_path points to valid Oracle credentials with appropriate permissions to list tables and run queries.
Troubleshooting¶
- Missing table name: If you select get_table_columns or suggest_joins without a table_name, set table_name and rerun.
- Unknown action: If you see an "Unknown action" error, ensure action is one of discover_tables, get_table_columns, suggest_joins, or build_query.
- No results returned: Verify target_schema and table_name exist and your credentials have access. Try discover_tables first to confirm visibility.
- Connection or auth errors: Confirm credentials_path is correct and valid for the Oracle instance. Test with the Oracle Test Connection node or verify network access.
- Timeouts: Increase timeout for large schemas or complex queries, or reduce result size by narrowing the request.