Hi Amit,
(however remember that hash-index does not support transactions)
This has been fixed a few days ago, so you will have transaction support
if you use the last snapshot
Best regards,
Artem Orobets
* Orient Technologiesthe Company behind OrientDB*
2014-05-26 10:47 GMT+03:00 Artem Orobe
Hi Amit,
RID generation scheme can change anytime in future and the goal is to not
> have north bound system any impact of such a thing..
What do you mean by this?
How does that impacts the other system?
Does the north bound system may store record identities somewhere?
Lookup by RID is highly
Hi Artem,
Thanks for your reply. I am not sure if I should attempt to copy the ID
into the UUID or not... what is recommended... ?
Here are my additional thoughts...
1. RID from OrientDB exposed to north-bound systems may create trouble when
data underneath is moved to different clusters etc
2
I see. So what would be the best approach to copy the ID of the vertex just
created into another property named UUID ?
On Tuesday, May 20, 2014 1:29:39 AM UTC-7, Artem Orobets wrote:
>
> Hi Amit,
>
> An explicit call toString() may brake your graph consistency.
>
> You are doing the changes in tr
Hi Amit,
An explicit call toString() may brake your graph consistency.
You are doing the changes in transaction so ids of the elements are
temporary and will be updated during transaction commit. Explicit call
toString will prevent such update.
This also mean that you need to commit transaction
An explicit toString() call on getId() resolves this BTW.
e.g.
v.setProperty("uuid", v.getId().toString()); - this works for the expected
result. But I am not sure if that should be explicitly done ?
On Monday, May 19, 2014 11:44:58 PM UTC-7, Amit Kumar wrote:
>
> Dear Experts,
>
> I seem to ha
