Testing of inactive design-time artifacts

1. A system comprising:

a memory storing processor-executable process steps; and

a processor to execute the processor-executable process steps to cause the system to:

receive an instruction to commit a design-time artifact of a database server application and metadata associated with the design-time artifact to a repository of a database server;

associate the design-time artifact with a flag that indicates an active state of the design-time artifact or an inactive state of the design-time artifact, wherein the design-time artifact is a database procedure or an analytical view and wherein in a case that the design-time artifact is associated with a flag that indicates an inactive state, the metadata stored in the repository indicates that the design-time artifact is a test version of a second design-time artifact that is associated with a flag that indicates an active state;

store the design-time artifact in the repository of the database server in association with the flag;

set the flag to indicate the inactive state;

receive a request from a user to access the design-time artifact associated with the flag set to the inactive state; and

in response to the request, and based on the flag indicating the inactive state, generate a private runtime representation of the design-time artifact and deploy the private runtime representation of the design-time artifact for exclusive use by the user.

2. A system according to claim 1 , wherein the processor is further to execute the processor-executable process steps to cause the system to:

store a second design-time artifact in the repository of the database server in association with a second flag set to the inactive state; and

in response to the request, and based on the second flag indicating the inactive state, generate a second private runtime representation of the second design-time artifact, and deploy the second private runtime representation of the design-time artifact for exclusive use by the user.

3. A system according to claim 1 , wherein the instruction is received from the user.

4. A computer-implemented method comprising:

receiving an instruction to commit a design-time artifact of a database server application and metadata associated with the design-time artifact to a repository of a database server;

associating the design-time artifact with a flag that indicates an active state of the design-time artifact or an inactive state of the design-time artifact, wherein the design-time artifact is a database procedure or an analytical view and wherein in a case that the design-time artifact is associated with a flag that indicates an inactive state, the metadata stored in the repository indicates that the design-time artifact is a test version of a second design-time artifact that is associated with a flag that indicates an active state;

storing the design-time artifact in the repository of the database server in association with the flag;

setting the flag to indicate the inactive state;

receiving a request from a user to access the design-time artifact associated with the flag set to the inactive state; and

in response to the request, and based on the flag indicating the inactive state, generating a private runtime representation of the design-time artifact, and deploying the private runtime representation of the design-time artifact for exclusive use by the user.

5. A computer-implemented method according to claim 4 , further comprising:

storing a second design-time artifact in the repository of the database server in association with a second flag set to the inactive state; and

in response to the request, and based on the second flag indicating the inactive state, generating a second private runtime representation of the second design-time artifact, and deploying the second private runtime representation of the design-time artifact for exclusive use by the user.

6. A computer-implemented method according to claim 4 , wherein the instruction is received from the user.

7. A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause to the computer system to:

receive an instruction to commit a design-time artifact of a database server application and metadata associated with the design-time artifact to a repository of a database server;

associating the design-time artifact with a flag that indicates an active state of the design-time artifact or an inactive state of the design-time artifact, wherein the design-time artifact is a database procedure or an analytical view and wherein in a case that the design-time artifact is associated with a flag that indicates an inactive state, the metadata stored in the repository indicates that the design-time artifact is a test version of a second design-time artifact that is associated with a flag that indicates an active state;

store the design-time artifact in the repository of the database server in association with the flag;

set the flag to indicate the inactive state;

receive a request from a user to access the design-time artifact associated with the flag set to the inactive state; and

in response to the request, and based on the flag indicating the inactive state, generate a private runtime representation of the design-time artifact and deploy the private runtime representation of the design-time artifact for exclusive use by the user.

8. A medium according to claim 7 , wherein the program code is further executable by a computer system to cause to the computer system to:

store a second design-time artifact in the repository of the database server in association with a second flag set to the inactive state; and

in response to the request, and based on the second flag indicating the inactive state, generate a second private runtime representation of the second design-time artifact, and deploy the second private runtime representation of the design-time artifact for exclusive use by the user.

9. A medium according to claim 7 , wherein the instruction is received from the user.

10. The system of claim 1 , wherein in a case that the design-time artifact is associated with a flag that indicates an active state, the design-time artifact is compiled as a runtime object and is executed at runtime.

11. The system of claim 1 , wherein the user is a developer that committed the design-time artifact to the repository.

12. The system of claim 1 , wherein the received request comprises a request to access all design-time artifacts associated with a flag set to the inactive state.

13. The system of claim 1 , wherein the private runtime representation of the design-time artifact is associated with an application that comprises the design-time artifact associated with the flag set to the inactive state and wherein the private runtime representation of the design-time artifact associated with the flag set to the inactive state comprises execution of the application including the design-time artifact associated with the flag set to the inactive state.