Database Schema

Support for database design

Providing support for database schema design would allow :

• Model the data layer alongside the application layer
  (tabbed view, switch between UML class diagram and DB Schema design)

• Keep the entire system architecture in one tool

Proposed Functionality

Support core database concepts such as:

• Tables

• Columns with data types

• Primary keys

• Foreign keys

• Compound keys

• Relationship cardinality (1:1, 1:N, N:M)

• Self-referencing relationships

Iteration 2

• Default values

• Constraints (e.g., unique, not null)

• Views

• Materialized views

• Stored procedures

• Functions

• Triggers

Iteration 3

• Schemas / namespaces

• SQL DDL generation (CREATE TABLE, CREATE VIEW, etc.)
  Export to multiple dialects (PostgreSQL, MySQL, SQL Server, SQLite)

• Warn about circular dependencies

• Detect invalid foreign key references

I would roll it out in three iterations, the first being the simplest, then gauge if there is interest, if after iteration one you see that the features are not increasing engagement or sales I would stop there, but if you notice good feedback I would continue with iteration two, as for iteration three, that maybe a bit more ambitious.