Activating database-request statement caching for selected users
- Last Updated: January 16, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Activating database-request statement caching for selected users
When you choose to activate database-request statement caching for an individual user, the following menu appears:
|
Enter the number for the type, or Q to exit:
- 1-Single — Only the current ABL program and line number, or a single SQL statement is reported.
- 2-Stack — The call stack up to the current ABL program and line number.
- 3-One Time Request — The ABL or SQL client report tracing information once. Once reported, database-request statement caching is turned off.
- Q-Quit — Quit this function and return to the Client Database-Request Statement Caching menu.
After selecting the type, chose a user by number from a menu like the following:
|
Based on your entry, the following actions are performed:
- If the user number is valid, or if the user is specified in the list,
database-request statement caching is activated. If the user is a self-serve or remote
client, database-request statement caching is activated for that client. If the user
number represents a remote database server, database-request statement caching is
activated for all clients serviced by that database server. Note: Once activated, database-request statement caching can not be canceled. You must deactivate for selected users, all users, or all future users.
- You can continue entering additional valid user numbers.
- The user number entry is terminated when you press ENTER without specifying a valid numeric character, or when you press ENTER after entering a non-numeric character.