Ok thanks, I'll give it a try then. On Monday, January 19, 2015 at 4:36:59 PM UTC+1, Andrey Lomakin wrote: > > I thought about this as well, however, I think that if I'm using edges >> instead of storing the IDs itself (in graph mode), the relationship should >> be preserved even after an export/import. Is that right ? >> > > Yes, sure. > > On Mon, Jan 19, 2015 at 4:17 PM, Bertrand Quenin <[email protected] > <javascript:>> wrote: > >> The only issue is that if you do export database to JSON and then back >>> your RIDs will be changed. >>> >> >> I thought about this as well, however, I think that if I'm using edges >> instead of storing the IDs itself (in graph mode), the relationship should >> be preserved even after an export/import. Is that right ? >> >> >> On Monday, January 19, 2015 at 2:28:16 PM UTC+1, Andrey Lomakin wrote: >>> >>> Hi Bertran, >>> The only issue is that if you do export database to JSON and then back >>> your RIDs will be changed. >>> But may be we will add option to keep rids on their places. Not so hard >>> to do. >>> The only downside of such flag will be presence of holes for rids of >>> removed records. >>> Each record removal consumes about 10 bytes of disk space (not so much >>> )) ), but when you do export/import we optimize space is used by database >>> as result rids may be changed. >>> >>> On Mon, Jan 19, 2015 at 2:48 PM, Bertrand Quenin <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> I'm currently using OrientDB for a project at work and I have some >>>> question about record IDs. >>>> >>>> As far as I understood, record IDs are unique and can be used to to >>>> identify a record in a deterministic way. I was wondering if these IDs can >>>> be used to identify objects through (REST) APIs. >>>> >>>> As any web application, I need to identify objects one way or another >>>> and I was wondering what the best approach would be: >>>> 1/ Using record IDs provided by orient DB >>>> 2/ Adding a "business" id field to my objects and manage it aside. >>>> >>>> So far, I didn't see any reason why I shouldn't use the record ID >>>> itself, the only con I see is that RID are strings clusterId#position (and >>>> not plain integers) and it's a bit harder to expose in an URL ... >>>> >>>> Is there any issue I haven't foresee ? >>>> >>>> Thanks for your help >>>> >>>> -- >>>> >>>> --- >>>> 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/d/optout. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Andrey Lomakin. >>> >>> -- >> >> --- >> 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/d/optout. >> > > > > -- > Best regards, > Andrey Lomakin. > >
-- --- 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/d/optout.
