Abstract: In a method for storing and accessing objects in an electronic content store (e.g. for a Website), each object is assigned a version number, such that multiple instances of the same object with different version numbers may coexist. When accessing an object in the content store for reading or writing, a requested version number is specified. When reading an object, if an instance of that object with the requested version number exists in the content store, that instance of the object is returned, and otherwise the most recent older instance of that object is returned. When writing to an object, if an instance of that object with the requested version number exists in the content store, the write is performed to that instance of the object, and otherwise a copy is made of the most recent older instance of the object, the copy is assigned the requested version number, and the write is performed to the copy. This provides an efficient and convenient mechanism for managing versions of the content.
Abstract: In a method for storing and accessing objects in an electronic content store (e.g. for a Website), each object is assigned a version number, such that multiple instances of the same object with different version numbers may coexist. When accessing an object in the content store for reading or writing, a requested version number is specified. When reading an object, if an instance of that object with the requested version number exists in the content store, that instance of the object is returned, and otherwise the most recent older instance of that object is returned. When writing to an object, if an instance of that object with the requested version number exists in the content store, the write is performed to that instance of the object, and otherwise a copy is made of the most recent older instance of the object, the copy is assigned the requested version number, and the write is performed to the copy. This provides an efficient and convenient mechanism for managing versions of the content.
Abstract: A first version of object data for an object instance can be stored in an object persistence store, which can be a distributed store. After the first version of the object data is stored, a second version of the object data can be stored in the store, without deleting the first version of the object data. Object data versioning information that identifies the first version of the object data and the second version of the object data can be stored separately from method versioning information for the object instance. After the second version of the object data is stored, a request to retrieve the first version of the object instance can be received, and in response, the first version of the object data can be retrieved from the store. Multiple versions of the object instance data can also be searched.
Type:
Application
Filed:
September 17, 2010
Publication date:
March 22, 2012
Applicant:
Microsoft Corporation
Inventors:
Raymond R. Patch, Daniel K. Lin, Rajeev S. Chauhan
Abstract: A software object model for modeling (resource instances and resource types in a network management system. The model comprises object instances and object classes. Each class comprises fragments of data and/or program code and is a generalization of one or more object instances. The model models each resource type by an object class and assigns to the class a class version identifier which indicates at least some capabilities of the resource instance/types and a collection of the fragments included in the class of the version in question. The model further models each resource instance by an object instance of the corresponding class, and assigns to the instance an object instance identifier and an instance version identifier which indicate the version of the class used for modeling the resource type in question.
Type:
Grant
Filed:
December 27, 2002
Date of Patent:
March 20, 2007
Assignee:
Nokia Corporation
Inventors:
Jyrki Kaski, Uwe Geuder, Otso Auterinen, Esa Nurmi, Stefan Zohren
Abstract: Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.
Abstract: Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.
Abstract: Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.
Abstract: Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.
Abstract: Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.
Abstract: Using a versioning feature of an authoring application to back up multiple versions of a stored object in single, version-enabled instance stored on backup media is disclosed. In some embodiments, an indication is received that a subsequent version data associated with an object an existing instance of which is stored in a backup storage location is to be backed up. A version control mechanism of an authoring application that created or updated the object as stored in a primary storage location is invoked to incorporate the subsequent version data into the existing instance of the object as stored in the backup storage location.
Abstract: Methodologies for upgrading and patching an in-database application package and its application instances. A data platform determines a number of objects of an application instance running on the data platform at a previous version level of an application package of the application instance. In response to determining the number of objects of the application package running on the data platform at the previous version level of the application package is one or more, the data platform continues determining the number of objects running on the data platform at a previous version level of the application package. In response to determining the number of objects of the application instance running on the data platform at the previous version level of the application package is none, the data platform upgrades the application instance to the new version of the application package.
Type:
Application
Filed:
September 20, 2023
Publication date:
August 22, 2024
Inventors:
Damien Carru, Jeremy Yujui Chen, Pui Kei Johnston Chu, Benoit Dageville, Scott C. Gray, Unmesh Jagtap, Subramanian Muralidhar
Abstract: Methodologies for upgrading and patching an in-database application package and its application instances. A data platform determines a number of objects of an application instance running on the data platform at a previous version level of an application package of the application instance. In response to determining the number of objects of the application package running on the data platform at the previous version level of the application package is one or more, the data platform continues determining the number of objects running on the data platform at a previous version level of the application package. In response to determining the number of objects of the application instance running on the data platform at the previous version level of the application package is none, the data platform upgrades the application instance to the new version of the application package.
Type:
Grant
Filed:
February 15, 2023
Date of Patent:
October 31, 2023
Assignee:
Snowflake Inc.
Inventors:
Damien Carru, Jeremy Yujui Chen, Pui Kei Johnston Chu, Benoit Dageville, Scott C. Gray, Unmesh Jagtap, Subramanian Muralidhar
Abstract: A method includes comparing a first layout of data elements associated with a first version of a class and a second layout of data elements associated with a second version of the class. The first and second versions of the class are associated respectively with first and second versions of assembly code. The method also includes updating method information in an existing object instance associated with the first version of the class if the first and second layouts are identical. In addition, the method includes creating a new object instance associated with the second version of the class and transferring one or more values of one or more data elements from the existing object instance to the new object instance when the first and second layouts are not identical.
Abstract: A software object model for modelling resources (resource instances (RI) and resource types (RT)) in a network management system. The model comprises object instances (OI) and object classes (OC). Each class comprises fragments (FG) of data and/or program code and is a generalization of one or more object instances (OI). The model models each resource type (RT) by an object class (OC) and assigns to the class a class version identifier (CVI) which indicates at least some capabilities of the resource (RI, RT) and a collection of the fragments (FG) included in the class (OC) of the version in question. The model further models each resource instance (RI) by an object instance (OI) of the corresponding class, and assigns to the instance (OI) an object instance identifier (OII) and an instance version identifier (IVI) which indicate the version of the class (OC) used for modelling the resource type (RT) in question.
Type:
Application
Filed:
December 27, 2002
Publication date:
July 24, 2003
Inventors:
Jyrki Kaski, Uwe Geuder, Otso Auterinen, Esa Nurmi, Stefan Zohren
Abstract: A method includes comparing a first layout of data elements associated with a first version of a class and a second layout of data elements associated with a second version of the class. The first and second versions of the class are associated respectively with first and second versions of assembly code. The method also includes updating method information in an existing object instance associated with the first version of the class if the first and second layouts are identical. In addition, the method includes creating a new object instance associated with the second version of the class and transferring one or more values of one or more data elements from the existing object instance to the new object instance when the first and second layouts are not identical.
Abstract: Automated maintenance of an object repository file for use in automation testing of a web application. A current instance of an identifier and current instance of an object locator, for an element of the application, are generated based on a current version of the application. If the current instance of the object locator is not found, but the current instance of the identifier is found, in historical data generated based on a historical version of the application, the element is marked for an update of its object locator. Historical attributes data of the element are updated with current attributes data extracted from a current version of the application; a new instance of the object locator for the element is generated based on the updated attributes data of the element; and the object repository file is updated using the new instance of the object locator for the element.
Abstract: Described are methods and systems related to creating an instance of an adaptable business object for a business scenario. A scenario specific action node is received to perform the business scenario. Based upon a scenario specific action node identifier of the received scenario specific action node, an adaptable business object is identified. A dimension version associate with the identified adaptable business object is determined. Based upon a dimension code of the dimension version, metadata of the dimension version is retrieved. Business logic that is operable for creating an instance of the adaptable business object for the dimension version is identified. Based upon the identified business logic, the metadata of the dimension version and the adaptable business object are compiled to create the instance of the adaptable business object for the dimension version.
Type:
Application
Filed:
August 20, 2009
Publication date:
February 24, 2011
Inventors:
WEN GU, Bin Fu, Sergio Lencinas, Jesus Lopez Mijan
Abstract: A method for loading objects from hash chains. A version chain of a class for a serialized object is located in an instance block of an instance chain. A class version of the serialized object is compared to a current version of the class. When the class version of the serialized object matches the current version of the class, a runtime object is loaded by deserializing the serialized object. When the class version of the serialized object does not match the current version of the class: one or more field values are extracted from the serialized object; a converter function is applied to the one or more field values to generate one or more converted field values; and a runtime object that matches the current version is loaded with the one or more converted field values.
Abstract: A method for loading objects from hash chains. A version chain of a class for a serialized object is located in an instance block of an instance chain. A class version of the serialized object is compared to a current version of the class. When the class version of the serialized object matches the current version of the class, a runtime object is loaded by deserializing the serialized object. When the class version of the serialized object does not match the current version of the class: one or more field values are extracted from the serialized object; a converter function is applied to the one or more field values to generate one or more converted field values; and a runtime object that matches the current version is loaded with the one or more converted field values.
Abstract: An in-database application package and application instance for a data platform. The data platform creates an application instance of an application package having a versioned schema, creates one or more system roles for the application instance, creates a user role and an administrator role for the application instance, creates one or more objects of the application instance based on a versioned schema, and grants one or more use privileges to the one or more roles. Application instances of the application package are upgraded or patched on the data platform based on application package versions. To ensure a proper upgrade or patch, the data platform tracks versions of executing objects of application instances in a call context.
Type:
Application
Filed:
November 30, 2023
Publication date:
August 15, 2024
Inventors:
Karol Pawel Bienkowski, Damien Carru, Jeremy Yujui Chen, Pui Kei Johnston Chu, Benoit Dageville, Scott C. Gray, Unmesh Jagtap, Subramanian Muralidhar