| Oracle® Database Application Developer's Guide - Workspace Manager 10g Release 2 (10.2) Part Number B14253-01 |
|
|
View PDF |
| Oracle® Database Application Developer's Guide - Workspace Manager 10g Release 2 (10.2) Part Number B14253-01 |
|
|
View PDF |
This section describes new and changed Workspace Manager features for Oracle Database 10g Release 2 (10.2).
For all DBMS_WM procedures that accept a where_clause parameter, only primary key columns can be specified in the WHERE clause, except in a subquery. The subquery can refer to columns that are not primary keys, but it cannot refer to a version-enabled table.
In previous releases, the WHERE clause could contain only primary key columns, and and it could not contain a subquery.
The DBMS_WM functions and procedures are documented in Chapter 4.
The following new DBMS_WM procedures are related to valid time support:
SetWMValidTimeFilterON and SetWMValidTimeFilterOFF set and remove a valid time filter for the current session. A valid time filter is a time that is applied to queries against version-enabled tables that have valid time support. When a valid time filter is set for the current session, only rows that are valid for the specified time are returned.
SetWMValidUpdateModeON and SetWMValidUpdateModeOFF enable and disable sequenced update and delete operations on tables that have valid time support.
These procedures are documented in Chapter 4.
The ALL_WORKSPACES and USER_WORKSPACES views contain the new column MP_ROOT_WORKSPACE, which contains the name of the root workspace of the multiparent graph if the workspace is part of a multiparent graph.
These views are documented in Chapter 5.
The new DBA_WM_VT_ERRORS view contains information about the error that occurred during the last call to the DisableVersioning, CommitDDL, or RecoverFromDroppedUser procedure.
This view is documented in Chapter 5.
The SetWorkspaceLockModeON and SetWorkspaceLockModeOFF procedures now accept the auto_commit parameter.
These procedures are documented in Chapter 4.
The SetValidTime procedure accepts only the validFrom and validTill parameters. The validFromFormat and validTillFormat parameters are no longer supported.
You can now drop database users that own one or more version-enabled tables. However, immediately after dropping any such users, you should call the new RecoverFromDroppedUser procedure, which is documented in Chapter 4.
You can now grant table-level privileges on version-enabled tables to users, and you can revoke such privileges.
See Section 1.8 for information about DDL operations on version-enabled tables.
