Skip to content
Tinker
Download

Objects, builder and server

The views that show a database as a whole rather than one table at a time.

Objects overview

Double-click a database or schema to open Objects: tables, views, materialized views, partitioned tables, functions and procedures with their signatures.

One row per object: name, kind, estimated rows, size, engine (MySQL), collation, owner (PostgreSQL) and comment. Every figure comes from the introspector; nothing here runs COUNT(*). The footer says so: “Row counts are the server’s estimates, not a count”. A search field filters by name, any column sorts, and the context menu offers Open, Structure, Copy DDL and Drop.

Visual query builder

Drag tables onto the canvas; foreign keys become joins. The SQL on the right updates as you go, and Preview runs it against the tab’s session.

⌘⇧B opens the builder. Tick the columns you want, add Where, Group, Having, Order and Limit clauses in the tabs below the canvas, and either open the result in a query tab or save it as a view. The generated SQL is fully quoted and schema-qualified, so it runs unchanged wherever you paste it.

Server view

Server Activity (⌘⇧A) lists sessions with their state, current statement and elapsed time, and lets you cancel or kill one. Users & Privileges (⌘⇧U) shows accounts and grants and can create a user. Settings shows the server’s configuration. Each view speaks the engine’s own catalog: pg_stat_activity and pg_roles, or information_schema.processlist and mysql.user.

What SQLite does not have

SQLite has no server, so several of the views on this page have nothing to show for it, and they say so rather than pretending. There are no users or privileges to manage, no sessions to watch or cancel, no stored routines, and no profiler. The Objects overview and the structure designer work exactly as they do elsewhere.

Maintenance

The table context menu offers Truncate, Drop, Rename and the engine’s maintenance operations (VACUUM and ANALYZE, or OPTIMIZE and ANALYZE TABLE). Destructive operations open a confirmation sheet; on a production connection the sheet requires the table name to be typed.