python - uuid with different languages -
on our system there's different routines different languages (mainly c++ , python) interacting on same database tables.
in python, uuid1 implementation (mac+time in ns) favorite since reduce (low still present) collision risk. mac address disclosing not problem in our context.
afaik, c++ implementation, boost lib instance, uuid4 equivalent (pseudo-random).
given implementation between uuid4 in python , c++ (or java if introduce in future) might different, suspect increase collision risks.
would mix python's uuid1 , c++/boost uuid4 ?
or go uuid4 on both language ?
or go uuid1 on both lib boost...
p.s.
proposed "duplicate question" not address question since newid , guid.comb not uuid1 nor uuid4 compliant (they mix time-based , pseudo-random bytes)
Comments
Post a Comment