Before connecting Oracle
TTSQL's Oracle adapter requires Erlang ODBC, an ODBC driver manager and an installed Oracle Instant Client ODBC driver on the TTSQL server. Selecting Oracle as the project dialect does not install those runtime dependencies.
Provide host, port, database connection identifier, username and password, plus the configured driver name where necessary. Confirm the service connection string and schema ownership with your database administrator; network reachability and database grants are separate prerequisites.
Give the prompt the right dialect and context
Oracle folds unquoted identifiers to uppercase; double-quoted identifiers retain their exact case. String values use single quotes. Use the actual owner when referring to tables outside the connected user's schema.
Oracle DATE stores a time of day as well as the calendar date. DATE '2026-02-01' is midnight, so use a half-open range to include a full month. TIMESTAMP supports fractional seconds; be explicit about time zone conversion when your source type carries a zone.
Schema used in these examples
customers(id INTEGER PRIMARY KEY, name TEXT, country TEXT); orders(id INTEGER PRIMARY KEY, customer_id INTEGER REFERENCES customers(id), ordered_at TIMESTAMP, status TEXT, total DECIMAL(12,2)). Each order has one customer. total is the order amount in a single reporting currency; paid means recognized revenue in this teaching dataset. Timestamps use UTC. These are example tables, not tables TTSQL creates.
Translate TEXT and TIMESTAMP to equivalent column types for your engine. Use your own database, schema and table qualifiers. Each example states its reporting grain and sorting rule.
Review these Oracle details
Oracle treats an empty string as NULL for character data. A predicate status = '' will not identify missing statuses; use IS NULL when that matches the requirement.
Use explicit date literals or bind values rather than implicit string-to-date conversion. A query that happens to work with one NLS_DATE_FORMAT can fail or change meaning under another session configuration.
Generate, review, then choose whether to run
Select the matching database type and confirm your project's schema context before generating. Review the returned SQL against the schema and the metric you intended. A successful connection test does not prove that every table or operation is authorized.
TTSQL's POST /api/v1 endpoint generates SQL and returns executed: false. Query execution is a separate manual Run action in the workspace, subject to the configured connection and policies. The examples below are educational SELECT statements, not live results from your database.
Official Oracle references
Check your engine version and account configuration when adapting a function or connection setting.