HTMLdb Developer
Dev console
Everything you reach for in TOAD, in a browser tab. A SQL worksheet that knows your schema, a results grid built for work, every object type, jobs, sessions, locks and storage, AI review, and a Git flow that takes code from DEV to TST to PRD by pull request.
Every feature of Dev console, and how its security works.
Find anything
- Schema tree with live counts and invalid objects in red
- Recent objects, newest first
- Compile invalid: recompile everything, rebuild unusable indexes online, a time limit per object
- The header shows DEV, TST or PRD in its own colour
SQL worksheet
- Run the statement at the cursor, or the whole script
- Alias + dot lists the columns; two tables suggest the join
- F4 describes any name, in the editor or in a result cell
- Bind variables, a Commit switch, Format, Explain
- Ctrl+U / L / I change case; Ctrl+B comments; Ctrl+H replaces
- Drop a file to load it; drag a column heading in for its name
Results grid
- Keyboard navigation and copy, cell or row
- Fixed columns behind a divider you can drag
- Find duplicates across every row
- Sort and filter with a live timer and Stop
- Edit data in place; CSV and JSON in one click
Objects
- Packages, procedures, functions, triggers and types: edit, compile, run
- Tables and views: columns, data, indexes, constraints, triggers, DDL
- Where used (through synonyms), what it uses, grants, synonyms
- Export a schema's DDL to a zip
Jobs, sessions, locks, storage
- Run any SQL as a scheduler job and watch it live
- Every job: run log, changes, next runs, run now, rebuild as a script
- Sessions and their SQL, locks and who blocks whom
- Tablespaces and datafiles, resize and autoextend
AI built in
- Review a procedure or a whole package; big ones go in parts
- Ask for a change and get a diff to apply
- Paste screenshots into the request
- Suggest indexes from an execution plan
Git, pull requests, promotion
- A repo per database; Commit and Promote start on the right one
- Compare, AI security review, Merge or Send back with reasons
- Sent-back work shows on the object in DEV
- APEX apps, pages and static files in the same flow
Security
Signed in with App Builder
Every page and every request checks the APEX session and that the browser is signed in to App Builder as a developer of the workspace. Nothing runs before that check.
Nothing trusted from the browser
Requests are POSTs to the package that owns them. The user and workspace come from the checked session; names, paths and keys are validated before they reach SQL or a URL.
Secrets stay on the server
API keys, OAuth tokens and certificates are stored AES-256 encrypted with a fresh IV for every value. The browser only ever learns whether a secret is set.
