[JAVA-281] when dropping a database or a collection, they remain in the driver cache, which can lead to problems Created: 24/Feb/11  Updated: 17/Mar/11  Resolved: 24/Feb/11

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5

Type: Bug Priority: Major - P3
Reporter: Antoine Girbal Assignee: Antoine Girbal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

this may lead to issue if it's recreated later.
For example write concern and query options will not take new values from mongo.
Or the authentication data from DB object.



 Comments   
Comment by auto [ 24/Feb/11 ]

Author:

{u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}

Message: JAVA-281: still need to ignore error due to ns not existing
https://github.com/mongodb/mongo-java-driver/commit/40aec21bf4156f49943cb912a8c89ab8c2cc4335

Comment by Antoine Girbal [ 24/Feb/11 ]

db is removed from cache in Mongo.java
collection is removed from cache in DbApiLayer.java
removed the caching set seenCollections in DB.java since it does not really provide any feature.

Comment by auto [ 24/Feb/11 ]

Author:

{u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}

Message: JAVA-281: when dropping a database or a collection, they remain in the driver cache, which can lead to problems
https://github.com/mongodb/mongo-java-driver/commit/6f91dc93ad8e85bd1e3be4c321d231cb8bccdd6a

Generated at Thu Feb 08 08:51:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.