LogoLogo
DoltHubBlogDiscordGitHubDolt
  • Introduction
    • What Is Dolt?
    • Installation
      • Linux
      • Windows
      • Mac
      • Build from Source
      • Application Server
      • Docker
      • Upgrading
    • Getting Started
      • Version Controlled Database
      • Git For Data
      • Versioned MySQL Replica
    • Use Cases
      • Data Sharing
      • Data and Model Quality Control
      • Manual Data Curation
      • Version Control for your Application
      • Versioned MySQL Replica
      • Audit
      • Configuration Management
      • Offline First
  • Concepts
    • Dolt
      • Git
        • Commits
        • Log
        • Diff
        • Branch
        • Merge
        • Conflicts
        • Remotes
        • Working Set
      • SQL
        • Databases
        • Schema
        • Tables
        • Primary Keys
        • Types
        • Indexes
        • Views
        • Constraints
        • Triggers
        • Procedures
        • Users/Grants
        • Transactions
        • System Variables
      • RDBMS
        • Server
        • Backups
        • Replication
    • DoltHub/DoltLab
      • Permissions
      • Pull Requests
      • Issues
      • Forks
  • SQL Reference
    • Running the Server
      • Configuration
      • Access Management
      • Branch Permissions
      • Backups
      • Garbage Collection
      • Metrics
      • Replication
      • Troubleshooting
    • Version Control Features
      • Using Branches
      • Merges
      • Querying History
      • Using Remotes
      • Procedures
      • Functions
      • System Tables
      • System Variables
      • Saved Queries
    • SQL Language Support
      • Data Description
      • Expressions, Functions, Operators
      • Supported Statements
      • MySQL Information Schema
      • Collations and Character Sets
      • System Variables
      • Miscellaneous
    • Supported Clients
      • Programmatic
      • SQL Editors
    • Benchmarks and Metrics
      • Correctness
      • Latency
      • Import
  • CLI Reference
    • Commands
    • Git Comparison
  • Architecture
    • Overview
    • Storage Engine
      • Commit Graph
      • Prolly Trees
      • Block Store
    • SQL
      • Go MySQL Server
      • Vitess
  • Guides
    • Cheat Sheet
    • Contributing
      • dolt
      • go-mysql-server
    • MySQL to Dolt Replication
    • Importing Data
    • Integrations
  • Other
    • FAQ
    • Roadmap
    • Versioning
  • Products
    • Hosted Dolt
      • Getting Started
      • Notable Features
      • SQL Workbench
      • Cloning a Hosted Database
      • Using DoltHub as a Remote
      • Infrastructure
    • DoltHub
      • Data Sharing
      • API
        • Authentication
        • SQL
        • CSV
        • Database
        • Hooks
      • Continuous Integration
        • Getting Started
        • Workflow Reference
      • Transform File Uploads
      • Workspaces
    • DoltLab
    • Dolt Workbench
    • DoltgreSQL
Powered by GitBook
On this page
  • What are workspaces?
  • How are they be used?

Was this helpful?

Edit on GitHub
Export as PDF
  1. Products
  2. DoltHub

Workspaces

PreviousTransform File UploadsNextDoltLab

Last updated 1 year ago

Was this helpful?

What are workspaces?

Workspaces are a concept we invented for editing data on DoltHub. There is not a GitHub equivalent. Essentially workspaces are a special type of ref, similar to or . They are meant to simulate a "staging area" on DoltHub, similar to in Dolt.

Workspaces are shareable and temporary. Make any change to your database without affecting the state of your database. When you're satisfied with your changes you can commit them to a branch or create a pull request. If you're not satisfied with your changes, you can delete the workspace without any repercussions.

How are they be used?

Workspaces are automatically created when you run a write query from the SQL Console on a DoltHub database page.

You immediately see the history of queries that have been run within the workspace. From here, there are a few actions you can take:

  1. View the cumulative and current diffs

Diffs are useful for seeing exactly how your queries affected your data.

  1. Run more queries

Any query run from the SQL Console within the workspace will be added to the workspace. You can also view the data table from within the workspace (by running a SELECT query or clicking the "View data table" button) to use cell buttons to make changes.

  1. Delete the workspace

Clicking on the trash icon on the top right in your workspace will delete it and your changes. This will have no consequences to the rest of your database.

  1. Create a pull request or commit

  1. Come back to the workspace later

If you don't want to decide right away what you want to do with your workspace, you can come back to it later by clicking on "1 open workspace" at the top of the SQL Console.

You can also share the workspace link with teammates and have them contribute to your workspace.

The Cumulative Diff tab shows all changes made to the workspace since it was created from the main branch (also known as a between main and the tip of the workspace).

The Current Diff tab shows the change from the most recent commit on the workspace (or the between HEAD and its parent).

Either create a from the workspace by clicking on the "Create pull request" button, or click on the arrow to change the button to "Commit directly" to create a on the main branch (or whatever branch you created the workspace from).

three dot diff
two dot diff
pull request
commit
branches
working sets
tags