Abstract:
In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.
Abstract:
A hierarchical template framework may include lower tier templates that identify groups of software components for discrete software services. The template framework also may include upper tier templates that include one or more lower tier templates and identify software components for a prearranged group of the software services configured to support and operate with an associated category of core software functions. A software developer may build a software application from the software components identified in a selected upper tier template, lower tier templates, and any other core software components identified for the core software functions. The templates prevent the software developer from having to manually locate and test all of the software components for different software services used in a software application.
Abstract:
A hierarchical template framework may include lower tier templates that identify groups of software components for discrete software services. The template framework also may include upper tier templates that include one or more lower tier templates and identify software components for a prearranged group of the software services configured to support and operate with an associated category of core software functions. A software developer may build a software application from the software components identified in a selected upper tier template, lower tier templates, and any other core software components identified for the core software functions. The templates prevent the software developer from having to manually locate and test all of the software components for different software services used in a software application.
Abstract:
An exemplary embodiment of a multi-tenant database system is provided. The system includes a multi-tenant database, an entity definition table, and a data processing engine. The database has database objects for multiple tenants, including an existing object for a designated tenant. Each entry in the existing object has a respective entity identifier. The definition table has metadata entries for the database objects, including a metadata entry for the existing object. This metadata entry has a tenant identifier for the designated tenant, an entity name for the existing object, and an old key prefix for the existing object. Each entity identifier of the existing object begins with the old key prefix. The engine performs a data truncation operation on the existing object by updating the metadata entry to replace the old key prefix with a new key prefix. This results in an updated object that is identified by the new key prefix and the tenant identifier.
Abstract:
Terminating user access to database systems is described. A system receives, from a user interface associated with a system administrator, a request to terminate access by a user of a database system. The system terminates access by the user to the database system, without deleting an account associated with the user from an association with data and/or a workflow associated with the database system.
Abstract:
In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.
Abstract:
A method of establishing personalized limits on a search responsive to a key word query in an enterprise search system is described that includes receiving an object types access history for a particular user. Applying this method, the object types access history includes records of object types selected from search results returning multiple object types and records of object types selected via interfaces other than search results. The method continues with determining and storing in computer readable memory a personalized scope of object types. The personalized scope of object types sets a limit on object types initially returned by an enterprise search system for the particular user in response to key word queries by the particular user that do not specify object types to search.
Abstract:
A method of establishing personalized limits on a search responsive to a key word query in an enterprise search system is described that includes receiving an object types access history for a particular user. Applying this method, the object types access history includes records of object types selected from search results returning multiple object types and records of object types selected via interfaces other than search results. The method continues with determining and storing in computer readable memory a personalized scope of object types. The personalized scope of object types sets a limit on object types initially returned by an enterprise search system for the particular user in response to key word queries by the particular user that do not specify object types to search.
Abstract:
An exemplary embodiment of a multi-tenant database system is provided. The system includes a multi-tenant database, an entity definition table, and a data processing engine. The database has database objects for multiple tenants, including an existing object for a designated tenant. Each entry in the existing object has a respective entity identifier. The definition table has metadata entries for the database objects, including a metadata entry for the existing object. This metadata entry has a tenant identifier for the designated tenant, an entity name for the existing object, and an old key prefix for the existing object. Each entity identifier of the existing object begins with the old key prefix. The engine performs a data truncation operation on the existing object by updating the metadata entry to replace the old key prefix with a new key prefix. This results in an updated object that is identified by the new key prefix and the tenant identifier.
Abstract:
In accordance with embodiments, there are provided mechanisms and methods for versioning content in a database system using content type specific objects. These mechanisms and methods for versioning content in a database system using content type specific objects can enable embodiments to provide a database system which stores information associated with multiple versions of content. The ability of embodiments to provide a database system which supports content versioning can enable an efficient and comprehensive storage of content types having different features by the database system.