Hi, 

One idea (not sure if it will work) 

You can take 

Time primUTCMicrosecondsClock

when system start, then increase it sequentially. 
most probably that will ensure uniqueness while providing fast ids. 

but of course, that depends, you need to check in your system. 

I'm thinking on provide different ID generators for Voyage, and let people plug 
what is more convenient for them. 

(all of this happens because, unlike other db drivers, mongo does not answer 
the inserted id :( )

Esteban

On Aug 30, 2013, at 5:41 PM, Sabine Knöfel <sabine.knoe...@gmail.com> wrote:

> So, I will wait and till then, use the solution of Jan. 
> Thank you, Jan for the file in.
> Sabine
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705821.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 


Reply via email to