How to edit columns, keys, indexes and triggers, write T-SQL for views and procedures, create objects and delete them.
Changes are made to your copy of the schema. Nothing reaches the database until you run a
migration script yourself.
Editing a table
Select a table to open its editor below the diagram. It has six sections, each showing a
count:
Definition — the table's name and schema.
Columns — add, delete, reorder and retype columns, and set nullability,
identity and defaults.
Primary key — choose which columns are in the key.
Foreign keys — add and delete relationships, and set their referential
actions.
Indexes — add and delete indexes.
Triggers — add and delete triggers, each edited as T-SQL.
Sections you open stay open as you move between tables. You can also add a relationship by
dragging from one box to another on the diagram.
If the Indexes or Triggers section says they are unknown, the project was
saved before they were read. Select Refresh in the project menu to load them.
Editing a view, function or procedure
Select it to open its T-SQL. Edit the script, then select Check script and update
diagram to apply it. Until you do, your typing is a draft and the schema keeps the
previous version.
The check reports:
Syntax errors, with the line and column.
SELECT * with no FROM.
Tables and views named in the script that are not in your schema.
A script that creates an object with a different name from the one you are editing.
Column names inside the script are not checked. A script can pass the check and still fail on
a misspelled column when you run it.
Renaming one of these objects rewrites the CREATE line of its script to match.
Creating an object
Select + New under the filter box. It creates the kind of object shown on
the open tab.
The object appears on the diagram straight away, marked with an amber dot in the list.
Select Keep to file it, or Cancel to remove it.
Until you select Keep, the object is not in your migration script. You can
create several objects in a row, but changing object type, opening another object or redrawing
the diagram asks you to keep or cancel them first.
Deleting
There is no undo anywhere in WoodFireERD.
A table is deleted from its editor, not from the diagram. You are asked
to confirm, and told which foreign keys the deletion removes. Its triggers go with it.
Tables that point at it are not deleted.
A relationship is deleted by clicking its line on the diagram and
selecting Delete relationship. Both tables it joined stay on the
diagram.
A column, key, index or trigger is deleted from its section in the table
editor.