I have a non-responding image with the original code (with the signal) 2016-05-25 15:14 GMT+02:00 Holger Freyther [via Smalltalk] < ml-node+s1294792n4897346h21@n4.nabble.com>:
On 25 May 2016, at 15:42, Esteban Lorenzano <[hidden email] <http:///user/SendEmail.jtp?type=node&node=4897346&i=0>> wrote:
Hi,
No I donât⦠in part because is not me who make that code, but also because it is expected: after, you have:
getCollection: aString ^ [ self addCollection: aString capped: false size: nil max: nil ] on: MongoCollectionAlreadyExists do: [ :err | MongoCollection database: self name: aString ]
so the idea is to refine the error to separate MongoCollectionAlreadyExists so it can later be catch and handled properly.
when adding capped collection support it seemed like a good idea to fail if a collection already exists that might not be capped, but given the follow up issues I wonder if I/we should restore the original behavior that just ignored all errors?
holger
------------------------------ If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exists... To start a new topic under Pharo Smalltalk Users, email ml-node+s1294792n1310670h65@n4.nabble.com To unsubscribe from Pharo Smalltalk Users, click here <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&nod...> . NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant...>
-- View this message in context: http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exists... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.