Skip to content

Conversation

@asnare
Copy link

@asnare asnare commented Aug 27, 2014

ClosedDatabaseException on subsequent database access.

As discussed briefly in pull request #7, currently clients can continue to access the database even after it has been closed. This prevents that, and should also help ensure the underlying database is garbage collected.

This pull request is against master, and conflicts trivially with pull request #7. (Whichever is merged second will require a slight modification.)

…row ClosedDatabaseException on subsequent database access.

Currently clients can continue to access the database even after it has been closed. This prevents that, and should also help ensure the underlying database is garbage collected.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.15%) when pulling a69181e on divolte:drop-buffer-on-close into 0b91040 on maxmind:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.15%) when pulling 096a204 on divolte:drop-buffer-on-close into 0b91040 on maxmind:master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants