🚚 Export to Laravel Migrations

You can now export your database schema directly as Laravel migration files. Each table will be self-contained within its own migration class, and its file name automatically set to match Laravel's convention. Behind the scenes, this is powered by Jason's awesome Laravel Shift Blueprint package.

Kickstart that next app feature even quicker now. It's even easier now to transition from designing your database models in DrawSQL to your scaffolding your Laravel codebase, without having to recreate those table and columns again.

You'll find this in the revamped export modal:

We're keen to support exports to other frameworks as well, prioritized based on its popularity among DrawSQL users. Have an export format in mind? Suggest or add your vote in the roadmap here: https://drawsql.app/roadmap 


📝Table comments, and for columns as well

One that has been a popular request since the beginning of times, today we've launched table and column notes.

This lets you leave comments for your teammates (or self) for any table and columns. 

Hopefully you'll find this one helpful and as always keen to hear any feedback.

📺 Presentation mode

Sometimes it's useful to view a read-only version of your database diagram in full-screen with maximum screen real-estate. Useful for example when presenting In team discussion and tech meetings. This new presentation mode lets you do just that!

Works on your embeds too! We've used it in our recently launched template gallery, see this template of Laravel Spark for an example.


🖼️ Database schema gallery

This had been in the works for 2-months now, it's finally launched! The gallery is a collection of 200+ database schemas of open-source packages, useful as references when architecting your app's next feature. If you haven't seen it, check it out here. You can still suggest more diagrams, I plan to continuously grow the library with more schema diagrams.

Thanks to all of you that supported the launch, it went surprisingly well 🤯:

  • Featured on ProductHunt homepage for the day - Link
  • #3 on Hacker News - Link

Also gathered tons of feedback from the new users on the day, excited to work on them especially the popular ones. Presentation (full-screen) mode, and table notes would probably be next, stay tuned!

📥Clone into existing diagrams

Previously you could clone any of your diagrams to start a new diagram. With this update, you now have a new option to append the cloned diagram into any of your existing diagrams, even into a diagram of another team (as long as you have the right permissions there).

Works for any template diagrams in our template gallery (that's coming soon) as well! 

🎞️Embeds

Embed your database diagrams anywhere on the web!

That means it's much easier to include your DrawSQL database schema as part of your documentation now (e.g. in Confluence, Notion or any others), and not have to worry about syncing changes to keep it up-to-date. Some users have also started using this in their blog and Medium posts!

For now it's still missing the frontend 😬, eventually you'll get a nice interface to copy the embed code to copy directly to your site.

The frontend is ready now, just click on the 'share' dropdown in the top nav to get started!


🧮Support composite indexes and keys

Announcing support for composite primary & unique keys, as well as composite indexes comprising of multiple columns.

We're really excited for this one! To be honest, this took much longer than we'd like. What you're seeing is actually our 3rd-rebuild of the feature since we really wanted to nail the UX, by providing this additional functionality without compromising the minimal uncluttered feel of both the editor and canvas.

Also, the specified composite key/index supports ordering of the columns within. In most cases order won't matter, but in those few instances where it does for your app, it's good to know that your covered.

Let us know what you think, if you see anyway this can be improved further.

🧭Public roadmap

🤔💭Got a feature request or feedback for DrawSQL? It's now even easier to surface those thoughts on the newly launched roadmap: https://roadmap.drawsql.app/

The roadmap also offers more transparency on what's in progress and what's in the pipeline. You can also upvote if you like an idea proposed by others.

Always love hearing from users!

🕰️Diagram Versioning

It's sometimes useful to tag 'checkpoints' for your diagram as it evolves, so that you can preview the previous state of a diagram, and revert to it if required.

We've got that covered now - you can now version your database diagrams!

Just tag a new version at any time:

And now you have a list of versions

🔒 This advanced feature is restricted to the 'growth' and 'enterprise' plan (yup they have just been renamed 😉). Upgrade now if you're not on these plans to gain access.

🕹️Editor configs - Defaults for new table color and column datatype

New workflow shortcut - You can now define defaults that will be automatically applied when you create new tables and columns. We're launching 2 of them now:

  1. Default table color
  2. Default column datatype

These can be configured within the new diagram settings popup within the editor.

This will be the last update to wrap up an awesome year. We're very excited for 2020 and have heaps planned, with the core of it to continue work with our loyal users drive new features, with every step to towards making DrawSQL the best tool for creating, planning and documenting your database schema.

Thanks for following along the journey 🙏, could not be where we are today without you. Happy new year 2020! 🎊🎉🍻 🎆

Show Previous EntriesShow Previous Entries