Oracle 视图 DBFS_CONTENT 官方解释,作用,如何使用详细说明
本站中文解释
FEED
Oracle视图 DBFS_CONTENTFEED 提供了和 Oracle 内容管理的文件系统接口(File System Interface,FSI)相关的内容在数据库视图(database view)层次上的表示。它支持原子操作,也就是在文件系统层次上可以实现一些复杂的操作,而不会因为一些中间步骤失败而导致失败。
使用 DBFS_CONTENTFEED 视图,用户可以受益于 Oracle 内容管理中的多种优点,比如查询、SQL 优化等;同时,用户可以使用标准 SQL 语句检索存储在 Oracle 内容库中的文件,从而实现更加简单、高效的文件管理。用户可以使用 SQL 语句来搜索 Oracle 内容管理数据库中的文件,也可以把文件系统中的文件导入到 Oracle 内容管理库中进行统一管理,从而有效地管理公司的数据和文档资源。
官方英文解释
DBFS_CONTENT
displays all the path items from all available content stores in the system.
Column | Datatype | NULL | Description |
---|---|---|---|
|
|
Name of store |
|
|
|
Location at which instance of store is mounted |
|
|
|
Name of path to item |
|
|
|
Type of path item (see |
|
|
|
BLOB locator that can be used to access data in the path item |
|
|
|
Time of last access of a path name’s contents |
|
|
|
Access Control List (in standard ACL syntax) |
|
|
|
Time of last change to the path name |
|
|
|
Number of child directories/folders a directory/folder path has (this property should be available in providers that support the |
|
|
|
One or more client-supplied mime-types (in standard RFC syntax) describing the path name which is typically of |
|
|
|
Time at which the item was created. Once set, this value remains the same for the lifetime of the path name. |
|
|
|
Set to a nonzero number if the path name has been soft-deleted but not yet purged (see |
|
|
|
Store-specific unique identifier for a path name. Clients must not depend on the GUID being unique across different stores, but a given (store-name, store-specific-path name) has a stable and unique GUID for its lifetime. |
|
|
|
Time of last change to the data associated with a path name. Changes to the content of a |
|
|
|
Client-supplied (or implicit) owner name for the path name |
|
|
|
Store-specific unique identifier for the parent of a path name. Clients must not depend on the GUID being unique across different stores, but a given (store-name, store-specific-path name) has a stable and unique GUID for its lifetime. The GUID of the parent of this path name (that is that std_parent_guid(pathname) == std_guid(parent(pathname))). |
|
|
|
Content of the symbolic link of a |
|
|
|
Type of hash provided in the |
|
|
|
Hash value of type |
|
|
|
Number of compatible locks placed on a path name. If different principals are allowed to place compatible (read) locks on a path, the |
|
|
|
Client-supplied user-data associated with a user-lock, uninterpreted by the store |
|
|
|
One or more implicit or client-specified principals that applied a user-lock on a path name |
|
|
|
One of the ( |
|
|
|
Sequence number for linear versioning of a path name |
|
|
|
Version path name for hierarchical versioning of a path name |
|
|
|
A provider-generated store-specific unique contentID in the form of a string for a file element (that may optionally not be associated with a path (see |
See Also:
-
Oracle Database PL/SQL
Packages and Types Reference for more information about DBMS_DBFS_CONTENT Constants – Path Name Types and DBMS_DBFS_CONTENT Constants – Store Features -
Oracle Database PL/SQL
Packages and Types Reference for more information about the DBMS_CRYPTO package