Patent classifications
G06F16/213
METHODS AND SYSTEMS FOR TRANSACTIONAL SCHEMA CHANGES
Methods and systems for executing transactional schema changes at a database are provided. The method includes receiving, at a gateway node of a cluster of database nodes, a statement corresponding to a schema of a database stored by the cluster, wherein a parent transaction comprises the statement, the statement comprises a schema change operation to modify the schema, and a first version of one or more versions of a descriptor comprises the schema. The method includes generating, by the parent transaction and using one or more child transactions, a version of a synthetic descriptor comprising an updated schema with an added schema element configured to be available for the parent transaction. The method includes writing the synthetic descriptor as an updated version of the descriptor, wherein the updated version comprises the updated schema with the added schema element in a publicly available state. The method includes committing the parent transaction.
ZERO DOWNTIME EVOLUTION OF DATABASE SCHEMAS FOR CLOUD APPLICATIONS
In an example embodiment, a first version of a cloud-based application is deployed. The first version of the cloud-based application contains references, based on a first schema, to a first database. Then a second version of the cloud-based application, different than the first version, is deployed. The second version of the cloud-based application contains references, based on a second schema, to the first database. Then access to the second version of the cloud-based application to one or more user devices is prevented while permitting testing devices to have access to the second version of the cloud-based application, while migrating data from the first schema of the first database to the second schema of the first database. Then access to the second version of the cloud-based application to the one or more user devices is permitted once the migrating of the data is complete.
DATABASE MODIFICATION USING A SCRIPT COMPONENT
Technologies are provided for database modification using a script component. In some embodiments, a method comprises executing, by a computing system comprising at least one processor, a script component comprising one or more functions to transform a database. The method also includes modifying, by the computing system, the database based on at least one transformation defined by the one or more functions in response to executing the script component.
Database Schema Branching Workflow, with Support for Data, Keyspaces and VSchemas
A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.
SYSTEM AND METHOD FOR TRANSITION OF STATIC SCHEMA TO DYNAMIC SCHEMA
Systems and methods that provide a mechanism to transition static schema to dynamic schema while maintaining backwards capability. Simple removal of static schema elements, followed by replacement with dynamic schema elements, make a third-party code incompatible since the third-party code references schema entities that no longer exist. Provided is a mechanism to decrease the memory use of non-material static schema entities. Transitioning static schema to dynamic schema allows the database to avoid loading non-material schema entities, thereby decreasing overall memory usage.
Database dual-core storage system based on optical disk and method using the system
A database dual-core storage system based on optical disk comprises a server, a magnetic disk storage device and an optical disk storage device connecting to the server via data connection, a database management system, a data processor and a data connector installed on the server, wherein the database management system is arranged for completing database management and data management of the magnetic disk storage device and the optical disk storage device in response to data requests; the data processor is arranged for configuring fields of a database base core and fields of a database extension core, writing data of corresponding fields into the database base core and the database extension core respectively in response to data requests; the data connector is arranged for creating data connection between the database base core and the database extension core in response to data requests. The integrity and safety of data are guaranteed.
Client-Side Automated Application Programming Interface (API) Mapping
A system, method and product for client-side automated application programming interface (API) mapping of a computerized system. The method comprises creating a mapping by: detecting, by a client-side agent that is operated on a client device executing a frontend of the computerized system, an invocation by a first application of the API function of a second application, wherein the API function is defined by a function prototype comprising a domain of potential values for an input or output parameter of the API function; and based on information gathered by the client-side agent, automatically determining a logical schema of the API function, wherein the logical schema defining a logical function prototype comprising a sub-domain of the domain of potential values, wherein the sub-domain restricting at least one value of the domain.
PLATFORM MANAGEMENT OF INTEGRATED ACCESS OF PUBLIC AND PRIVATELY-ACCESSIBLE DATASETS UTILIZING FEDERATED QUERY GENERATION AND QUERY SCHEMA REWRITING OPTIMIZATION
Various techniques are described for platform management of integrated access of public and privately-accessible datasets utilizing federated query generation and query schema rewriting optimization, including receiving at a dataset access platform a query formatted according to a first data schema, generating a copy of the query, saving the query and the copy to a datastore, parsing the copy of the query in the first schema using an inference engine, determining whether the query comprises data associated with an access control condition associated with accessing the dataset, the access control condition being configured to indicate whether the query is permitted to access the dataset, and rewriting, using a proxy server, the copy of the query in a second schema, and optimizing the rewriting by identifying a database engine to execute the query and including other data converted into another triple associated with an attribute of the query.
TRANSPORT OF MASTER DATA DEPENDENT CUSTOMIZATIONS
A method, a system, and a computer program product for transporting master data dependent configuration data for execution of a transaction. A request to import a transaction data from a first computing system to a second computing system is received. The transaction data is associated with execution of a transaction by the second computing system. Based on the received request, a determination that a first type of data is required for execution of the transaction by the second system. The first type of data includes one or more keys identifying dependencies of the first type of data on a second type of data. One or more transport objects for transporting the transaction data from the first to the second system are generated. The transaction data identifies the first and second types of data and the keys. The transaction is executed using the transport objects imported to the second system.
Zero downtime evolution of database schemas for cloud applications
In an example embodiment, a first version of a cloud-based application is deployed. The first version of the cloud-based application contains references, based on a first schema, to a first database. Then a second version of the cloud-based application, different than the first version, is deployed. The second version of the cloud-based application contains references, based on a second schema, to the first database. Then access to the second version of the cloud-based application to one or more user devices is prevented while permitting testing devices to have access to the second version of the cloud-based application, while migrating data from the first schema of the first database to the second schema of the first database. Then access to the second version of the cloud-based application to the one or more user devices is permitted once the migrating of the data is complete.