Hi Ted, is not a bug, but rather a way to avoid a concurrent problem when a client deletes the record while another one is creating it.
Lvc@ On 28 April 2014 00:43, Ted Smith <[email protected]> wrote: > I create a new record (@version =1) and immediately delete it > then immediately create a new record, I found the new record @version is 2, > instead of 0, even though rid shows it is indeed a new record. > > I thought the @version is tied to a record, so when creating a new record, > should it be always 1? > > > > -- > > --- > 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. > -- --- 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.
