Hi, Andrey: Perhaps I could present the question differently, There are two ways for db recovery purpose,
one is to use OrientDB provided backup/restore console command (or api) for this option, would RID be guaranteed to be the same after restore from the zip file? The other is to use export/import command, according to wiki doc the import command is import database <input-file> [-preserveClusterIDs = <true|false>] If I set the preserve to be true, would RID be guaranteed preserved during import? Thanks very much. On Wednesday, February 19, 2014 3:24:49 AM UTC-5, Andrey Lomakin wrote: > > Hi, > It is impossible now but we can go in other way why do you need to keep > rids after export/import do you have some external links ? > > > On Wed, Feb 19, 2014 at 5:45 AM, TedS <[email protected] > <javascript:>>wrote: > >> Hi: >> >> From what I read, record id can almost be used as a primary key except >> that it will change >> during importing, for the purpose of simplifying DBA work. Is there >> possibility >> to have option (some extra config/chores would be fine) to force the >> import process >> to retain all the RID info? This would help a lot with performance >> compared to having >> to create a separate primary key, just for the sake of preventing import >> issue. >> >> Thanks >> >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Best regards, > Andrey Lomakin. > > Orient Technologies > the Company behind OrientDB > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
