Database schema branching workflow, with support for data, keyspaces and VSchemas

At least one non-transitory computer-readable storage medium for maintaining version control for databases in a database version tracking system, with branching support for database schemas, the at least one non-transitory computer-readable storage medium storing computer executable instructions that, when loaded into computer memory and executed by at least one processor of a computing device, cause the computing device to perform the following steps:

• creating a first branch of a main database from the database version tracking system;
• wherein the first branch further comprises a copy of the main database in a specific state, as recorded in the database version tracking system, the copy being created in a workspace isolated from the database version tracking system, the copy comprising at least a copy of a schema of the main database in a specific state;
• responsive to receiving a control signal from a user associated with the first branch indicating to merge a changed version of the first branch back into the database version tracking system, determining differences between a current version of the main database as tracked by the database version tracking system and the changed version of the first branch;
• wherein determining differences between the current version of the database and the changed version of the first branch further comprises generating at least one schema diff;
• determining, from the at least one schema diff, whether merging the changed version of the first branch back into the database version tracking system creates a conflict;
• responsive to determining that merging the changed version of the first branch back into the database version tracking system does not create a conflict, merging the changed version of the first branch back into the database version tracking system;
• wherein merging the changed version of the first branch back into the database version tracking system further comprises performing at least one schema operation from a group of schema operations consisting of:
• create table, drop table and alter table, the at least one schema operation being indicated by the at least one schema diff;
• creating a second branch of the main database from the database version tracking system;
• wherein the second branch further comprises a copy of the main database separate from the copy comprising the first branch, the separate copy being created in a workspace isolated from the database version tracking system, the copy comprising at least a copy of the schema of the main database in the specific state;
• responsive to receiving a control signal from a user associated with the second branch indicating to merge a changed version of the second branch back into the database version tracking system, determining differences between the changed version of the first branch and the changed version of the second branch, relative to a version of the main database as tracked by the database version tracking system from which the first branch and the second branch were generated;
• wherein determining differences further comprises generating at least one schema diff, wherein generating at least one schema diff further comprises:
• generating a first schema diff of the version of the main database as tracked by the database version tracking system from which the first branch and the second branch were generated and the changed version of the first branch;
• creating a first temporary schema based on the first schema diff;
• generating a second schema diff of the first temporary schema and the changed version of the second branch;
• creating a second temporary schema based on the second schema diff;
• generating a third schema diff of the version of the main database as tracked by the database version tracking system from which the first branch and the second branch were generated and the changed version of the second branch;
• creating a third temporary schema based on the third schema diff;
• generating a fourth schema diff of the third temporary schema and the changed version of the first branch;
• and
• creating a fourth temporary schema based on the fourth diff;
• determining, from the at least one schema diff, whether merging the changed version of the second branch back into the database version tracking system on top of the changed first version of the first branch creates a conflict;
• and
• responsive to results of the determining, performing a step from a group of steps consisting of:
• responsive to determining that merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch does not create a conflict, merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch, the merging further comprising performing at least one schema operation from a group of schema operations consisting of:
• create table, drop table and alter table;
• and
• responsive to determining that merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch does create a conflict, not merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch.

A computer system for maintaining version control for databases in a database version tracking system, with branching support for database schemas, the computer system comprising:

• at least one processor;
• computer memory;
• program code for creating a first branch of a main database from the database version tracking system;
• wherein the first branch further comprises a copy of the main database in a specific state, as recorded in the database version tracking system, the copy being created in a workspace isolated from the database version tracking system, the copy comprising at least a copy of a schema of the main database in a specific state;
• program code for, responsive to receiving a control signal from a user associated with the first branch indicating to merge a changed version of the first branch back into the database version tracking system, determining differences between a current version of the main database as tracked by the database version tracking system and the changed version of the first branch;
• wherein determining differences between the current version of the database and the changed version of the first branch further comprises generating at least one schema diff;
• program code for determining, from the at least one schema diff, whether merging the changed version of the first branch back into the database version tracking system creates a conflict;
• program code for, responsive to determining that merging the changed version of the first branch back into the database version tracking system does not create a conflict, merging the changed version of the first branch back into the database version tracking system;
• wherein merging the changed version of the first branch back into the database version tracking system further comprises performing at least one schema operation from a group of schema operations consisting of:
• create table, drop table and alter table, the at least one schema operation being indicated by the at least one schema diff;
• program code for creating a second branch of the main database from the database version tracking system;
• wherein the second branch further comprises a copy of the main database separate from the copy comprising the first branch, the separate copy being created in a workspace isolated from the database version tracking system, the copy comprising at least a copy of the schema of the main database in the specific state;
• program code for, responsive to receiving a control signal from a user associated with the second branch indicating to merge a changed version of the second branch back into the database version tracking system, determining differences between the changed version of the first branch and the changed version of the second branch, relative to a version of the main database as tracked by the database version tracking system from which the first branch and the second branch were generated;
• wherein determining differences further comprises generating at least one schema diff, wherein generating at least one schema diff further comprises:
• generating a first schema diff of the version of the main database as tracked by the database version tracking system from which the first branch and the second branch were generated and the changed version of the first branch;
• creating a first temporary schema based on the first schema diff;
• generating a second schema diff of the first temporary schema and the changed version of the second branch;
• creating a second temporary schema based on the second schema diff;
• generating a third schema diff of the version of the main database as tracked by the database version tracking system from which the first branch and the second branch were generated and the changed version of the second branch;
• creating a third temporary schema based on the third schema diff;
• generating a fourth schema diff of the third temporary schema and the changed version of the first branch;
• and
• creating a fourth temporary schema based on the fourth diff;
• program code for determining, from the at least one schema diff, whether merging the changed version of the second branch back into the database version tracking system on top of the changed first version of the first branch creates a conflict;
• and
• program code for, responsive to results of the determining, performing a step from a group of steps consisting of:
• responsive to determining that merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch does not create a conflict, merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch, the merging further comprising performing at least one schema operation from a group of schema operations consisting of:
• create table, drop table and alter table;
• and
• responsive to determining that merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch does create a conflict, not merging the changed version of the second branch back into the database version tracking system on top of the changed version of the first branch.