Version History
Version History provides a chronological record of changes made to a database schema or project.
It helps teams understand how a database design has evolved over time by showing previous updates and the members who made them.
Version History improves collaboration by making project activity easier to review and understand.
Before you begin
Before viewing Version History, ensure that you have:
- Access to a Workspace
- Access to a Project
- Permission to view project history
[!NOTE] The available history depends on your project configuration and permissions.
What is Version History?
Version History records important changes made within a project.
Depending on your configuration, history may include:
- Database schema updates
- Table changes
- Column changes
- Relationship changes
- Project activity
- Member activity
View Version History
To review project history:
- Open a Project.
- Select Version History.
- Browse the available history entries.
- Select an entry to review its details.
History information
Each history entry may include:
| Property | Description |
|---|---|
| Date | When the change occurred |
| User | Member who made the change |
| Activity | Description of the change |
| Project | Related project |
| Database Schema | Related database schema |
Review changes
Version History helps you review:
- Recently updated schemas
- Database structure changes
- Team activity
- Design progress
Reviewing project history makes it easier to understand how the database evolved over time.
Benefits
Version History helps teams:
- Track project progress
- Understand design decisions
- Review previous work
- Improve collaboration
- Maintain project transparency
Best practices
- Review Version History before making major changes.
- Discuss significant database updates with your team.
- Keep project changes well organized.
- Maintain consistent database naming conventions.
[!TIP] Reviewing Version History regularly helps teams understand project evolution and improve collaboration.