![]() |
Cloudscape System Tables
|
Reference Manual |
SYSDEPENDSDescribes the dependency relationships between persistent objects in the database. Persistent objects can be dependents (they depend on other objects) and/or providers (other objects depend on them). When the user attempts to drop or modify a provider, Cloudscape checks to see if there are any current dependents. If there are, one of the following actions will occur:
Providers are tables, conglomerates, and constraints. Dependents are publications, views, and stored prepared statements.
IndexesThe following query returns the dependent object names and types and the provider names and types that they are dependent on:
SELECT dependentFinder.getSQLObjectName(dependentid) The following query returns all of the providers on which a view (Segments_Seatbookings) is dependent:
SELECT PROVIDERFINDER.getSQLObjectName(providerid) AS NOTE: Do not attempt to retrieve objects stored in the DEPENDENTFINDER and PROVIDERFINDER columns. Instead, call one of the documented methods on these columns as shown in the examples above. Marking Dependent Stored Prepared Statements InvalidStored prepared statements are "dependents"; that is, they depend on other dictionary objects, which are their "providers." When a provider is changed or dropped, Cloudscape marks the stored prepared statement invalid, thus requiring recompilation at the next execution. The invalidated target stored prepared statement is not recompiled until the next time the statement is executed. Each time a statement is recompiled (either deliberately or as a side effect of some other action), the LASTCOMPILED field of SYS.SYSSTATEMENTS is updated with the timestamp at the time of recompilation. |
|||||||||||||||||||||||||
|
![]() Cloudscape Version 3.6 For information about Cloudscape technical support, go to: www.cloudscape.com/support/.Copyright © 1998, 1999, 2000 Informix Software, Inc. All rights reserved. |