Oracle® Spatial Developer's Guide 11g Release 2 (11.2) Part Number E11830-11 |
|
|
PDF · Mobi · ePub |
The MDSYS.SDO_WFS_LOCK package contains subprograms for WFS support for registering and unregistering feature tables. Registering a feature table enables the table for WFS transaction locking; unregistering a feature table disables the table for WFS transaction locking.
To use the subprograms in this chapter, you must understand the conceptual and usage information about Web Feature Services (WFS) in Chapter 15.
Table 33-1 lists the WFS support subprograms.
Table 33-1 Subprograms for WFS Support
Subprogram | Description |
---|---|
Enables database transactions on WFS tables. |
|
Registers a feature table; that is, enables the feature table for WFS transaction locking. |
|
Unregisters a feature table; that is, disables the feature table for WFS transaction locking. |
The rest of this chapter provides reference information on the subprograms, listed in alphabetical order.
SDO_WFS_LOCK.EnableDBTxns();
Enables database transactions on WFS tables.
None.
This procedure overrides, through the end of the session, the WFS-T standard restriction against database transactions on WFS tables, so that any transaction with the current session ID can perform update and delete operations on WFS tables. Oracle Database triggers still check the WFS locks before the current transaction is allowed to modify a row; and so if a WFS transaction has a lock on a row, the triggers will not allow the operation to be performed. However, if there is no WFS lock on the current row, the triggers will allow the current transaction to modify the row.
You must call this procedure to perform certain operations when using Oracle Workspace Manager to version-enable a WFS table, as explained in Section 15.5. However, you can also use this procedure even if you do not use Workspace Manager with WFS tables.
For information about support for Web Feature Services, see Chapter 15.
The following example enables database transactions on WFS tables for the remainder of the current session.
BEGIN SDO_WFS_LOCK.enableDBTxns; END; /
SDO_WFS_LOCK.RegisterFeatureTable(
username IN VARCHAR2,
tablename IN VARCHAR2);
Registers a feature table; that is, enables the feature table for WFS transaction locking.
Name of the database user that owns the feature table to be registered.
Name of the feature table to be registered.
This procedure ensures that the necessary constraints for implementing WFS transaction semantics are associated with the feature table.
For information about support for Web Feature Services, see Chapter 15.
To unregister a table that has not been version-enabled, use the SDO_WFS_LOCK.UnRegisterFeatureTable procedure.
The following example registers the feature table named COLA_MARKETS_CS, which is owned by user WFS_REL_USER.
BEGIN SDO_WFS_LOCK.registerFeatureTable('wfs_rel_user', 'cola_markets_cs'); END; /
SDO_WFS_LOCK.UnRegisterFeatureTable(
username IN VARCHAR2,
tablename IN VARCHAR2);
Unregisters a feature table; that is, disables the feature table for WFS transaction locking.
Name of the database user that owns the feature table to be unregistered.
Name of the feature table to be unregistered.
This procedure disables, for the feature table, the constraints for implementing WFS transaction semantics.
The feature table must have been previously registered in a call to the SDO_WFS_LOCK.RegisterFeatureTable procedure.
For information about support for Web Feature Services, see Chapter 15.
The following example unregisters the feature table named COLA_MARKETS_CS, which is owned by user WFS_REL_USER.
BEGIN SDO_WFS_LOCK.unRegisterFeatureTable('wfs_rel_user', 'cola_markets_cs'); END; /