Release notes
What changed in ERDism, newest first. One entry per release — only changes you can see or use.
Latest
SQL import accepts more of your existing schemas
- NVARCHAR and NCHAR columns import. Columns declared as
NVARCHAR,NCHAR,NATIONAL CHARorNATIONAL VARCHARused to make the whole file fail. They now come in asVARCHARandCHARwith a UTF-8 character set, the way the database itself reads them. - Named primary keys stay primary keys. A primary key written as
CONSTRAINT name PRIMARY KEY (…)now comes in as the table's primary key. Before, the table arrived without one, and the import was rejected if any foreign key pointed at it. - INET6 columns in MariaDB projects. MariaDB projects now accept
INET6columns. - FLOAT and DOUBLE keep their precision. Types such as
FLOAT(7,3)andDOUBLE(10,2)keep the digits you wrote. Before, the import accepted them but the draft lost the digits and publishing was rejected. - mysqldump files import cleanly into MariaDB projects. MySQL-only version comments such as
/*!50705 … */are skipped, the way MariaDB skips them, so they no longer add columns or indexes that aren't in your database.
One-step Undo, a new home page, and a more accessible editor
- A new home page. The ERDism home page now walks through how your diagram stays current, how a team edits and approves changes, who else can read the schema, and everything else ERDism does — in English, Korean and Japanese.
- A welcome for new accounts. New users find a welcome message in the inbox, a getting-started panel in their workspace, an example project to explore, tips in an empty editor, and a list of keyboard shortcuts.
- Place assigned tables in one go. When tables are assigned to a diagram but none are on the canvas yet, a card offers Place all, which places and arranges them, or Place one by one.
- One action, one Undo. Place all, finishing an import, and creating a new project each undo with a single Undo, and Redo brings them back the same way.
- More of the editor works from the keyboard. A table moved with the arrow keys now keeps its new position. The table menu has Move to… as an alternative to dragging, Tab reaches the collapsed SQL panel, and Escape closes tooltips. Across the app, a skip link, page titles, focus that goes back where it was when a dialog closes, and larger touch targets make ERDism easier to use with a keyboard or a screen reader.
New look, easier canvas moves, docs in your language
- A new front page. The landing page is redesigned, with a clearer walk-through of what ERDism does and a quicker way into the live demo.
- A new ERDism logo. The app, the browser tab icon, and link previews use the new mark. A beta label sits next to the name while the public beta runs.
- See who is online. The member chips at the top of the workspace home now show only the people who are signed in right now, and change as they come and go. Click them to see every member, split into Online and Offline.
- Imported diagrams arrive arranged. Right after an import, tables are laid out the same way as Arrange by group. If the diagram already has tables, only the new ones are arranged, placed together near where you clicked — the tables you placed stay where they are.
- The public docs in Korean and Japanese. About, How it works, these release notes, and the legal pages can now be read in Korean and Japanese, and every docs link in the app opens the version in your display language. The Japanese legal pages are reference translations; the English version prevails.
Public beta
- ERDism is open as a public beta. Anyone can sign up and get a workspace. These notes start here; from now on, each change you can see or use is listed under the day it shipped.
- Bring in the schema you run, or draw a new one. Paste SQL or upload a file, see what the import would add, change, or remove, and choose which diagram each table goes on. Works with MySQL and MariaDB.
- One model, three views. The diagram, its SQL, and the inspector stay in step, so a change made in one shows up in the others. Each table keeps doc pages you write in Markdown.
- Every change on the record. The timeline shows who changed what, and when. Undo and Redo act only on your own changes, across every diagram in the project.
- Approve before you publish. A teammate approves or rejects each SQL block, only approved SQL is published, and each published version can be exported as a SQL file.
Looking for something specific? See every release on one page.