Another thing I was thinking about: We should probably also document the variables in the SYSTEM namespace (see RDB$GET_CONTEXT()) in the Context variables chapter. Or, maybe better (to avoid duplication and risk of divergence), make entries in that chapter and refer to RDB$GET_CONTEXT().
It concerns the following variables: DB_NAME NETWORK_PROTOCOL CLIENT_ADDRESS CURRENT_USER CURRENT_ROLE SESSION_ID TRANSACTION_ID ISOLATION_LEVEL ENGINE_VERSION (CURRENT_USER and CURRENT_ROLE are identical to their global namesakes, so they can be left out.) Paul ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
