Kbase 18303: Updates in one session may not be seen by ODBC RO connection
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/6/1998 |
|
Updates in one session may not be seen by ODBC RO connection
When connecting to a Progress Database Read Only (with -RO startup
parameter) through a Progress session or through an ODBC driver,
the Read Only session may not see changes made in another Progress
session. The Read Only session will only see changes made by other
users once those changes have been flushed out of the buffers and
are committed to the database, even though the 4GL transaction is
complete. When the session that is updating the database is
connected to the database in single user mode, the buffers are not
flushed until the session ends or another process flushes the
buffers. When the session that is updating the database is
connected to the database through a database server, the buffers
may not be flushed for up to an hour.
For example, if you connect to a Progress database single user and
create a record in the database and then connect to the same database
through an ODBC driver Read Only and try to read that record, it will
not be there. The single user session will need to end before a Read
Only connection will see this new record.