We heard you! Table Header Color and Table Group are now available in dbdocs! These two are well-loved features in dbdiagram, and are most requested by our dbdocs community.

With this, you can add a custom color to your table headers and group tables together to better organize your data models.

Table Header Color​

Choose a custom header color for each of your tables! This allows you to differentiate between tables and create more visually appealing documentation.

To set the header color for a table, use the following syntax:

Table ecomm_core.products [headercolor: #087f23] {
	...
}

Table Group​

Group tables together into categories! Keep your data models organized and maintain clean, clear documentation.

To group tables, use the following syntax:

TableGroup product_group {
  ecomm_core.products
  ecomm_core.product_tags
}

These features are immediately available for everyone. However, similar to dbdiagram, they might be moved to a paid offering when we introduce paid plans in dbdocs in the future.

Give them a try and let us know what you think!

Today, our team is bringing in a new feature: Diagram Export. Users now have the option to download their diagrams as PDF and PNG files.

Simply hover on the download button at the top-right corner of diagram views, then choose either PDF or PNG as your desired format.

Feel free to show some love or feedback in the feature announcement on our community.

After registration, your username is strictly set to your email or GitHub username. The constant username could be a problem for users who need specific usernames for organizational usage.

Therefore, we’re introducing a new CLI command to change your username (as well as your organization name). From the dbdocs CLI version 0.6.4, you can run dbdocs rename and freely switch to an available username.

Feel free to show some love or feedback in the feature announcement on our community.

dbdocs now supports Many-to-many Relationships!

When drawing the many-to-many relationship, you no longer need to create an associative (join) table. Instead, just define it directly, such as:

Table books {
  id int [pk]
  ...
}

Table authors {
  id int [pk]
  ...
}

Ref books_authors: books.id <> authors.id // many-to-many

For more DBML syntax updates, please check out our docs!

Today we provide you with another powerful tool for documenting your database - Multiple Schemas.

Previously you could only define the table names, and when loaded into dbdocs it falls into the default “public” schema.

Now, you can define the tables with full schema names:

Table ecommerce.products {
  ...
}

Moreover, you can make cross-schemas relationships and use enums from different schemas.

Table orders {
  id int [pk, ref: < ecommerce.order_items.order_id]
  status core.order_status
  ...
}

Enum core.order_status {
  ...
}

For more DBML syntax updates, please check out our docs!