Patent application number | Description | Published |
20100088274 | SYSTEM AND METHOD FOR SYNCHRONIZING A REPOSITORY WITH A DECLARATIVE DEFINTION - The subject disclosure relates to a method and system for synchronizing a repository with a declarative definition. The method and system includes receiving the declarative definition in which the declarative definition represents a constraint-based execution model. A script is also created that translates the declarative definition into machine code. At least one function is then performed on the repository in which the script provides instructions for the at least one function. | 04-08-2010 |
20100088283 | SYSTEM AND METHOD FOR MANAGING DATABASE APPLICATIONS - The subject disclosure relates to a method and system for managing a database application. The method and system include receiving a deployment package, which includes deployed objects of a declarative execution model and defining a plurality of data structures extracted from the deployment package such that at least one data structure populates an extended catalog. The deployed objects are then stored in a manner consistent with the plurality of data structures. | 04-08-2010 |
20100088350 | PACKAGING SYSTEM TO FACILITATE DECLARATIVE MODEL-DRIVEN DEVELOPMENT - The subject disclosure relates to a method and system for packaging a post-processed definition of a programming module. Contents of a constraint-based and/or order-independent execution model are received, in which the contents include a declarative source code. The contents are stored into an extensible storage abstraction such that the source code is stored in a declarative format. Metadata describing attributes of the contents stored in the extensible storage abstraction is also defined. A file is then created, which includes the extensible storage abstraction and the metadata. | 04-08-2010 |
20100088685 | SYSTEM AND METHOD FOR MAPPING A DOMAIN MODELING LANGUAGE TO A RELATIONAL STORE - A method and system for mapping between constructs in a domain modeling language and a relational storage language is provided. A source code authored in a source language is received and a set of constructs in the source code are identified. The set of constructs in the source code are mapped to a set of constructs in a target language. The source code is then compiled into a target code authored in the target language such that one of the source code or target code include a declarative constraint-based and/or order-independent execution model. | 04-08-2010 |
20100250623 | GENERIC EDITOR FOR DATABASES - Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema. | 09-30-2010 |
20110099188 | DATA FRAMEWORK TO ENABLE RICH PROCESSING OF DATA FROM ANY ARBITRARY DATA SOURCE - Accessing data in a data store at a field granularity. A method includes receiving a query from a user. The query specifies one or more non-unique fields of a record. The method further includes sending the query to a data store to retrieve the fields of the record at a field granularity. The method further includes receiving data for the one or more non-unique fields of the record at a field granularity. | 04-28-2011 |
20110307524 | UNIFIED CONCURRENT CHANGES TO DATA, SCHEMA, AND APPLICATION - Changes are managed in a multi-user database application environment. Proposed changes are collected, including changes to data, schema, and/or application descriptions. A user may specify foreign key relationships between items belonging to one or more of these categories. A view is produced showing the impact proposed changes would have on the environment if successfully committed. The user's proposed changes are ordered according to their dependencies, and submitted for committal together in a single transaction, subject to optimistic concurrency and consistency checks. For example, a proposed change to a data value may be inconsistent with a change which removed a data element containing the data value. The commitment operation may return identifiers and other return values, in addition to indicating whether the commitment was successful. | 12-15-2011 |
20120191650 | SYNCHRONIZING DATABASE PROJECTS WITH PARTNER PROJECTS - A solution authoring tool that includes an authoring environment that allows for the authoring of multiple projects of a solution including a database project that has a schema and a partner project that has a reference to the schema. When the database project is built and deployed, the database schema is made ready for runtime. When the partner project is built and deployed, the schema reference is provided within the partner software such that the partner software may interface with the database schema at runtime. To reduce or eliminate database schema drift at development time causing runtime errors at runtime, a model bus at least partially synchronizes changes made to the schema in the database project to the schema reference in the partner project, and vice versa. | 07-26-2012 |
20120221507 | DECLARATIVE UPDATE TO A LIVE SYSTEM - A live system manager may retrieve a current state of the live system, allow a user to edit the state, and generate a set of incremental commands that modify the current state into a desired state. The set of incremental commands may be then executed to create the desired state. In some embodiments, the set of incremental commands may be executed as a transaction. The live system manager may compare the current state to a desired state to generate the incremental commands, and may perform various validation operations during operation. A user may be presented options at various points to disambiguate the user's intentions. | 08-30-2012 |
20120323946 | DATA FRAMEWORK TO ENABLE RICH PROCESSING OF DATA FROM ANY ARBITRARY DATA SOURCE - Data is accessed and updated in a data store at a field granularity. A user query specifies one or more non-unique fields of a record. The query is sent to a data store to retrieve the fields of the record at a field granularity, in satisfaction of the query. The fields of the record can also be modified by transmitting a record ID along with original content, while omitting some of the record data, and by also including the modification to be made. | 12-20-2012 |
20130110879 | DECLARATIVE SUPPORT FOR REFERENCE DATA IN RELATIONAL DATABASES | 05-02-2013 |
20130117011 | TELEMETRY OF SYSTEM CHANGES - A telemetry system can parse and transform one or more change sets from a format intended to be processed by a computer to a form that is readily consumable by a human. The report or display generated to present the results can be customized for a particular domain. | 05-09-2013 |
20130117232 | SNAPSHOTS OF DATABASE MODELS - Methods, systems, and computer program products are provided for capturing snapshots of database models. Metadata of a database model is captured. A database model snapshot object is generated based on the captured metadata. The generated database model snapshot object is transportable, extensible, secure, and human readable. Furthermore multiple database model snapshot objects may be compared to each other to determine differences in database models in different database systems, to track how a database model of a database system is changing over time, to track how database source projects evolve over time and/or for other uses. | 05-09-2013 |
20130117733 | Simultaneously targeting multiple homogeneous and heterogeneous runtime environments - A single software project in an integrated development environment (IDE) may be built for multiple target environments in a single build episode. Multiple different output artifacts may be generated by the build process for each of the target environments. The output artifacts are then deployed to the target environments, which may be homogeneous or heterogeneous environments. The same source project may be used to generate multiple output artifacts for the same target environment. | 05-09-2013 |
20130173672 | GENERIC EDITOR FOR DATABASES - Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema. | 07-04-2013 |
20130232123 | DRIFT DETECTION AND NOTIFICATION - A drift condition, or change, in a data structure can be detected and communicated to one or more subscribers. Data structure can be monitored by periodic configurable polling of a data source or on demand polling. Upon detection of a change in the in the data structure, subscribers can be notified of the change and optionally other information such as the identity of the object that changed and nature of the change. | 09-05-2013 |
20140331213 | PACKAGING SYSTEM TO FACILITATE DECLARATIVE MODEL-DRIVEN DEVELOPMENT - The subject disclosure relates to a method and system for packaging a post-processed definition of a programming module. Contents of a constraint-based and/or order-independent execution model are received, in which the contents include a declarative source code. The contents are stored into an extensible storage abstraction such that the source code is stored in a declarative format. Metadata describing attributes of the contents stored in the extensible storage abstraction is also defined. A file is then created, which includes the extensible storage abstraction and the metadata. | 11-06-2014 |