Skeema v1.5.0 released
Skeema v1.5.0 has been released! This new version adds diff support for tables with check constraints, and also includes major enhancements to Skeema’s internal connection and query behaviors.
New online command reference
Skeema’s documentation has received a major overhaul, including a brand new command reference.
DB AMA video session with live demos
Join Skeema’s creator, Evan Elias, for a video discussion on August 11 at 8am PT! The session is part of the DB AMA series, and will include live demos and Q&A.
Skeema v1.4.0 released
Skeema v1.4.0 has been released! This new version includes diff support for partitioned tables and generated columns. Several other enhancements are included, especially for users with large-scale database deployments.
Skeema v1.3.0 released
Skeema v1.3.0 has been released! This new version primarily focuses on significant enhancements to Skeema’s linter, allowing users to customize the safeguards in their schema change workflow.
Automating Schema Changes at SendGrid
SendGrid’s Data Operations team recently rearchitected their MySQL schema change process. Their goal: safely empower the company’s individual engineering teams to manage their own schema changes, without requiring DBA intervention. Skeema is a key component of their new design.
Skeema v1.2.0 released
Skeema v1.2.0 has been released, including two major new features: support for stored procedures and functions, and improved linter functionality.
Coming soon: GitHub API Integration
Skeema’s command-line client is currently a stateless tool, typically run manually as needed. Some companies are starting to use it in an automated fashion, as part of a CI/CD pipeline, but this can be complex to configure. Fortunately, automated CI/CD using Skeema is about to become a lot easier!
Benefits of declarative schema management
Skeema uses a declarative approach to schema management: the repository reflects a desired end-state of table definitions, and the tool figures out how to convert any database into this state. This contrasts with most preexisting schema management systems, which instead are based on a concept of migrations: an incremental series of files, each defining a schema change operation and its corresponding rollback. In this post, we’ll discuss the differences in these approaches.