When any request invokes a stored procedure, the current definition for that stored procedure is copied at that moment to a metadata cache. On Classic server, this copy persists for the lifetime of the user’s connection. On Superserver, it stays “live” until the last connection is logged out.
A request comes from one of the following:
Effects of Changes
Once invoked, a trigger or stored procedure request persists in the metadata cache while there are clients connected to the database, regardless of whether any connected client makes use of the trigger or stored procedure. There is no mechanism to force these outstanding requests to update their metadata cache. For this reason, changes to PSQL modules are “deferred” to a greater or lesser extent in most cases. The ability of clients to see changes is different for Superserver than for Classic server.
Because existing requests are emptied from the metadata cache only when the last client disconnects from the database, they simply may never update on a 24/7 system. The only way to guarantee that all copies of stored procedures and triggers are purged from the metadata cache is for all connections to the database to terminate. When users log in again, they will all see the newest version of the stored procedure.
Altering or dropping a stored procedure takes effect immediately for new connections made after the change is committed. New connections that invoke the stored procedure will see the latest version. However, other connections continue to see the version of the stored procedure that they first saw. In practical terms, it makes sense to disconnect clients before you commit your changed module.
Firebird Related Interview Questions
|RDBMS Interview Questions||MySQL Interview Questions|
|Linux Interview Questions||Mac OS X Deployment Interview Questions|
|Windows Administration Interview Questions||Windows Server 2003 Interview Questions|
|SQL Interview Questions||NoSQL Interview Questions|
|Advanced C++ Interview Questions|
Introduction To Client/server Architecture
About Firebird Data Types
Date And Time Types
Blobs And Arrays
From Drawing Board To Database
Creating And Maintaining A Database
Firebird’s Sql Language
Expressions And Predicates
Querying Multiple Tables
Ordered And Aggregated Sets
Overview Of Firebird Transactions In
Programming With Transactions
Introduction To Firebird Programming
Developing Psql Modules
Error Handling And Events
Security In The Operating Environment
Configuration And Special Features
Interactive Sql Utility (isql)
Database Backup And Restore (gbak)
Housekeeping Tool (gfix)
Understanding The Lock Manager
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.