在执行操作时,读访问将被允许。
创建一个容器并且给它全局的读访问权限。
对节点和属性的读访问。
当遇到日志写满情况,仍允许对数据库的读访问。
When a log full condition is encountered, read access is still allowed on the database.
还授予对您已具有读访问权的每个内容项的读访问权。
This also grants read access to each content item that you have read access to.
还授予对您已具有读访问权的每个库组件的读访问权。
This also grants read access to each library component that you have read access to.
访问规则可以划分为两类:读访问规则和写访问规则。
Access rules can be divided into two categories: read access rules and write access rules.
还授予对您已具有读访问权的每个搜索规则的读访问权。
This also grants read access to each search rule that you have read access to.
还授予对您已具有读访问权的每个创作模板的读访问权。
This also grants read access to each authoring template that you have read access to.
还授予对您已具有读访问权的版本库中每一项的读访问权。
This also grants read access to each item in the version library that you have read access to.
还授予对您已具有读访问权的每种分类法和类别的读访问权。
This also grants read access to each taxonomy and category that you have read access to.
还授予对您已具有读访问权的每个站点和站点区域的读访问权。
This also grants read access to each site and site area that you have read access to.
还授予对每个用户信息的读访问权,但不能访问分类法和类别。
This also grants read access to each user profile, but no access to taxonomies and categories.
当用户试图读带安全标签的数据时,则应用读访问规则。
Read access rules are applied when a user attempts to read labeled data.
这有助于在查看审计日志或审计报告时明确区分读访问和写访问。
This helps me to identify straight away, when viewing the audit log or the audit report, if there has been a read or write access on the file.
这个BC至少需要对应该导入TM1的所有用户条目有浏览和读访问权。
This BC need to have browsing and read access to at least all the user entries which should be imported into TM1.
还授予对您已具有读访问权的每个工作流、工作流阶段和动作的读访问权。
This also grants read access to each workflow, workflow stage, and action that you have read access to.
LBAC使您可以决定谁拥有不同行和列上的写访问权限,谁拥有读访问权限。
LBAC lets you decide exactly who has write access and who has read access to individual rows and individual columns.
在大多数情况下,由于写访问非常复杂,因此数据联合模式主要用于进行读访问。
In most cases, the data federation pattern is used for read access because of the complexity of write access.
当对一个表运行RUNSTATS时,有两种用户访问选项:允许读访问和允许写访问。
There are two options for user access to a table while a RUNSTATS is running against that table: allow read access and allow write access.
在请求读访问和请求更新访问的事务之间产生冲突时,数据能否得到正确的保护是十分重要的。
It is important that this data is correctly protected from the competing requirements of those transactions that require read access, and those that require update access.
当用户读数据时(SELECT、UPDATE和DELETE操作),则应用读访问规则,读访问规则可总结如下。
The read access rules are applied when data is read (SELECT, UPDATE, and DELETE operations) and can be summarized as follows.
Policy——访问资源的规则,比如允许对多维数据集进行读访问,或者拒绝对Retailers维度的美国成员的祖先或后代成员进行读访问。
Policy - a rule for accessing a resource, such as allowing read access to a cube or denying read access to the ascendants and descendants of the U.S. members of the Retailers dimension.
WebSpherePortalV5.1.0.1引入的公共ModelSPI提供了对用于聚合和呈现门户内容的门户模型的读访问权。
The public model SPI introduced with WebSphere portal V5.1.0.1 provides read-access to portal models that are used to aggregate and render portal content.
许多WebSphereApplicationServer进程都需要对无数文件具有读访问权限,并且对log和transaction目录具有写访问权限。
Many WebSphere Application Server processes need read access to numerous files and write access to the log and transaction directories.
因为具有高symmetrix缓存读中率的工作负载都是以内存访问速度实现的,所以在EFD中存储所需要的数据可能不会对性能有大的改进。
Because workloads with high Symmetrix cache read-hit rates are serviced at memory access speed, storing the data needed on EFDs may not result in a significant increase in performance.
但其他用户能以读模式访问文件。
对于读和写访问,用户还可以拥有相同的标签。
A user can also have the same label for both read and write access.
如果不满足此条件,就拒绝读和写访问。
If this condition is not met, then read and write access is denied.
对于关系数据是如此,对于XML的读和写访问更是如此。
This is true for relational data, and even more so for XML read and write access.
应用推荐