Every FuiSQL release, newest first, with the features you can try. Screenshots use sample data.
Right-click any cell to jump to related records: up to the tables it belongs to, or down to the tables that refer to it. Click an invoice number, for example, and go straight to that invoice's lines, payments and distributions. A breadcrumb trail shows the path you took and takes you back.
A new command: give it two or more tables that are not directly related and it writes the join between them, filling in the tables in between.
SELECT *
FROM xla_ae_lines xal
JOIN xla_distribution_links xdl
ON xdl.ae_header_id = xal.ae_header_id
AND xdl.ae_line_num = xal.ae_line_num
-- seen in 10 queries
-- alternative (3 queries): xdl.ae_line_num = xal.ae_line_num
JOIN ap_invoices_all ai
ON ai.invoice_id = xdl.applied_to_source_id_num_1
-- seen in 1 query — WEAK, check this join
-- Filters usually applied with these tables (not applied here):
-- xal.application_id = 200 (with AP tables, 7 queries)
-- Alternative route via xla_ae_headers, xla_transaction_entities instead of xla_distribution_links (similar evidence; the two can differ in row grain):
-- xla_ae_lines -> xla_ae_headers: xah.ae_header_id = xal.ae_header_id (36)
-- xla_ae_headers -> xla_transaction_entities: xte.entity_id = xah.entity_id (4)
-- xla_transaction_entities -> ap_invoices_all: ai.invoice_id = xte.source_id_int_1 (2)The editor suggests the join condition after JOIN table alias, and after WHERE or AND when you list tables with commas. A join you have already written is not suggested again.
Name a table in FROM or JOIN and the editor offers a short alias that does not clash with the ones you already have.
The columns of the tables in your query are suggested as you type, most useful first, even before you have typed an alias. A column that exists on more than one table is suggested with its alias, so the SQL is never ambiguous. After WHERE and AND, joins and columns appear together in one list.
HZ_PARTIES), and how they relate. The first launch after updating rebuilds the schema once.FROM list.Missing-field messages now appear, saving no longer clears the form, cancelling a delete no longer hides the connection, and names with an apostrophe work.
FETCH FIRST, OFFSET, LIMIT, TOP) no longer gets a second limit added, which Oracle rejected.Write :parameter_name anywhere in a statement and a parameter bar appears below the editor with one input per parameter. Values are substituted when the query runs, so the same query can be re-run against different values without editing the SQL. The bar follows the statement at the cursor, so each query in a multi-statement file gets its own parameters.
IN (...) list accepts any number of values, entered as chips — press Enter or comma to add one, Backspace to remove the last.NUMBER columns unquoted, DATE and TIMESTAMP columns wrapped in TO_DATE / TO_TIMESTAMP with an explicit format mask, and everything else quoted and escaped. Text values keep their leading zeros, so an invoice number such as 0012 still matches.NLS_DATE_FORMAT setting.SYSDATE - 30, NULL or a sub-select.YYYY-MM-DD and DD-MON-YYYY, each optionally followed by a time. Ambiguous forms such as 01/02/2026 are rejected rather than guessed.:name inside a string literal or a comment is left untouched.