DBXDBX

Table Structure Editor

Edit table columns and indexes visually, then preview DDL before applying changes.

The table structure editor modifies columns, indexes, and some constraints for a single table. Use it for focused structure changes or to generate reviewable DDL without writing it by hand.

The structure editor is enabled for MySQL, PostgreSQL, SQLite, and SQL Server. Other databases may still expose DDL through the schema browser, but DBX does not show the visual editor when it cannot generate safe changes.

What You Can Edit

ObjectSupported Actions
ColumnsAdd and delete columns; MySQL/PostgreSQL can modify existing columns, and SQLite can rename columns
IndexesAdd indexes and delete existing non-primary indexes
CommentsMySQL/PostgreSQL can write column comments; PostgreSQL can write index comments

Database engines differ in DDL capabilities. DBX generates SQL for the active connection type.

Workflow

Open Table Structure

Right-click a table in the sidebar and open its structure view.

Edit Columns or Indexes

Add, modify, or remove columns and indexes in the visual editor. Changes are staged locally first.

Review SQL Preview

Before saving, review generated statements such as ALTER TABLE, CREATE INDEX, and DROP INDEX.

Apply Changes

Execute the SQL only after confirming it matches your intent.

Dropping columns, changing column types, and changing nullable constraints can affect existing data. Back up production databases first and confirm application code does not depend on the old structure.

Engine Differences

EngineNotes
MySQL / MariaDBAdd, delete, and modify columns; add and delete indexes
PostgreSQLRename columns, change type/default/nullability/comments, and add/delete indexes
SQLiteAdd, delete, and rename columns; more complex existing-column edits are blocked with a warning
SQL ServerFocused editor support for common table structure operations
Other enginesUse generated DDL, Schema Diff, or manual SQL when DBX does not expose the visual editor

Recommendations

  • Use the editor for small, focused changes
  • For large migrations, generate SQL and review it in your code repository
  • For environment sync, use Schema Diff
  • When impact is uncertain, back up first with Database Export

On this page