weapp-db-design

To generate a database ER diagram from user stories, you analyze product requirements to identify persistent entities, fields, and constraints, then output a Mermaid ER diagram. This process extracts data needs directly from user stories to ensure no entities are missed.

The best way to design a database schema for a WeChat mini program is to derive entities and relationships directly from product requirements and architecture documents. This ensures the database model remains consistent with existing structures and project needs.

Yes, this database design approach supports Django field conventions. It applies Django field standards during schema modeling and extension, while also incorporating necessary timestamp and soft-delete considerations into the generated Mermaid ER diagram.

To update an existing database model with new requirements, you extend or modify the current schema based on new user stories while maintaining consistency with existing class diagrams. The updated database design is then saved as a Mermaid ER diagram.

You should save the Mermaid ER diagram for full-stack workflow projects in the docs/design/db/models.mmd file. Saving the resulting database diagram here ensures it synchronizes properly with your architecture documents and project design.