Abstract: The described implementations relate to an access control framework for a database system. One implementation can receive, from a user, a request for data that identifies a resource, such as a view that obtains data from a database. The implementation can check the identity of the user to identify user roles associated with the user. The implementation can identify an access policy that is associated with the resource, and a rule that is associated with the access policy and applies to the user roles associated with the user. The rule can be applied to the request for data using attributes of the access policy. For example, if the request for data is a query on a view, the query can be rewritten to apply the rule.

Abstract: The described implementations relate to an access control framework for a database system. One implementation can receive, from a user, a request for data that identifies a resource, such as a view that obtains data from a database. The implementation can check the identity of the user to identify user roles associated with the user. The implementation can identify an access policy that is associated with the resource, and a rule that is associated with the access policy and applies to the user roles associated with the user. The rule can be applied to the request for data using attributes of the access policy. For example, if the request for data is a query on a view, the query can be rewritten to apply the rule.

Abstract: The described implementations relate to an access control framework for a database system. One implementation can receive, from a user, a request for data that identifies a resource, such as a view that obtains data from a database. The implementation can check the identity of the user to identify user roles associated with the user. The implementation can identify an access policy that is associated with the resource, and a rule that is associated with the access policy and applies to the user roles associated with the user. The rule can be applied to the request for data using attributes of the access policy. For example, if the request for data is a query on a view, the query can be rewritten to apply the rule.

Abstract: The described implementations relate to an access control framework for a database system. One implementation can receive, from a user, a request for data that identifies a resource, such as a view that obtains data from a database. The implementation can check the identity of the user to identify user roles associated with the user. The implementation can identify an access policy that is associated with the resource, and a rule that is associated with the access policy and applies to the user roles associated with the user. The rule can be applied to the request for data using attributes of the access policy. For example, if the request for data is a query on a view, the query can be rewritten to apply the rule.

Abstract: The described implementations relate to an access control framework for a database system. One implementation can receive, from a user, a request for data that identifies a resource, such as a view that obtains data from a database. The implementation can check the identity of the user to identify user roles associated with the user. The implementation can identify an access policy that is associated with the resource, and a rule that is associated with the access policy and applies to the user roles associated with the user. The rule can be applied to the request for data using attributes of the access policy. For example, if the request for data is a query on a view, the query can be rewritten to apply the rule.

Abstract: Many current computer software platforms support user customization and version upgradability. Unfortunately, upgrading a computer software platform may result in significant loss of user customization data. Additionally, it may be advantageous for users to export and import their customization data to share as customized business solutions with other instances of the computer software platforms. Accordingly, a technique for creating and importing a configuration package and a technique for creating and utilizing an update package is disclosed herein. The configuration package allows configuration data of elements within a computer software platform to be exported and imported. The update package allows elements to be exported within the update package. The update package may be utilized in upgrading, overwriting, and/or creating a new instance of elements. When an existing element is upgraded with an update element within the update package, the existing element's original configuration may be retained.

Abstract: Many current computer software platforms support user customization and version upgradability. Unfortunately, upgrading a computer software platform may result in significant loss of user customization data. Additionally, it may be advantageous for users to export and import their customization data to share as customized business solutions with other instances of the computer software platforms. Accordingly, a technique for creating and importing a configuration package and a technique for creating and utilizing an update package is disclosed herein. The configuration package allows configuration data of elements within a computer software platform to be exported and imported. The update package allows elements to be exported within the update package. The update package may be utilized in upgrading, overwriting, and/or creating a new instance of elements. When an existing element is upgraded with an update element within the update package, the existing element's original configuration may be retained.