Kbase P15932: How does the -RO feature impact LOCKING within schema holder when using DataServer?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
How does the -RO feature impact LOCKING within schema holder when using DataServer?
FIX:
THE PROGRESS SCHEMA HOLDER HAS NO INFLUENCE OVER LOCKING.
The prowin32.exe or _progres executable is the underlying process that ultimately makes the connection to the foriegn data-source. During connection, the clients connects to the schema holder, caches mapping information (determined by table references in the .r code) and then connects to the foriegn data-source.
The schema holder is a repository that holds the schema information of the foriegn data-source. The schema information includes such items as Progress datatype mappings, validation and trigger details. No data is ever stored within the schema holder. Because there is no data, Progress does not manage record locking.
When the -RO option is used, the metaschema files for the schema holder are in read only mode, thus they are not being locked, nor updated or used. The application simply reads the files from the disk.