You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add full support for protocol.LAST_COMMIT_INFO (#45)
Previously the LAST_COMMIT_INFO feature was only supported at the
protocol level: the driver always reported there was no information
available about the last commit.
Last commit ensures "read your own writes" capability for committed
transactions, even when connections are using different TEs.
Implement an internal structure to store last commit information:
- The information is saved as a process-wide set of data
- Allows the same process to connect to different databases, and to
connect to the same database multiple times (to the same or to
different TEs).
In order to support Python clients that may use threading with different
connections, use a Lock() to access the last commit details. Python
threading doesn't provide reader/writer locks; rather than write one
we'll use a simple mutex and assume this won't be a performance
bottleneck.
Add a reset() method to forget all information about previously
connected databases. This is not required since each database has its
own UUID, but can free up resources for long-running applications that
connect to lots of different databases.
0 commit comments