Read-only Media (-RO)
- Last Updated: January 17, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Read-only Media (-RO)
Use Read-only (-RO) to open a database for read-only access or to access a
database stored on read-only media (a read-only optical disk, for example).
| Operating system and syntax | UNIX / Windows |
-RO
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Client Connection | — | — | — | — |
If
you use the -RO parameter when other users are updating
the database, you might see invalid data, such as stale data or
index entries pointing to records that have been deleted.
A read-only session is essentially a single-user session. Read-only users do not share
database resources (database buffers, lock table, index cursors). However, unlike a normal
single-user database, a read-only database can be simultaneously accessed by multiple
-RO users.
When a read-only session starts, it does not check for the existence of a lock file for the database. Furthermore, a read-only user opens the database file, but not the log or before-image files. Therefore, read-only user activity does not appear in the log file.
If
a database is opened with -RO, the string returned by
the DBRESTRICTIONS function includes the keyword READ-ONLY.