OrientDB: RIDs assigned once and forever? -


imagine following:

  • a newly created node gets example rid #19:2
  • some time later node #19:2 gets deleted (so id theoretically available again)

now question is: there possibility/risk, rid #19:2 assigned again newly created node or can sure, won't assigned ever again?

luca garulli (founder , ceo of orientdb ltd) wrote here on so:

the rid (record id) never recycled.

but wise in general regard internal "implementation detail" whenever possible, if because @rid values might not survive export/import. (for reason, think nice have shorthand select <class> <id> = <value>)


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

css - Make div keyboard-scrollable in jQuery Mobile? -

ruby on rails - Seeing duplicate requests handled with Unicorn -