Hi,
I get this issue when I do massive and continues
parentModel.ChildModelList.clear() on nested lists of an object and
immediately calling addAll(new List) and this parentModel class has many
nested lists represented as LinkList in DB.
I am not getting this issue now as I modified the logic to
Hi guys,
Sorry could anybody provide a test case we can analyze and reproduce the
problem? I'd like to have this fixed in 2.0.5 ;-)
Lvc@
On 6 March 2015 at 20:20, Jing Chen wrote:
> I am getting this error too. Any progress on this issue? My application is
> running OrientDB 2.0.4
>
> Jing
>
>
I am getting this error too. Any progress on this issue? My application is
running OrientDB 2.0.4
Jing
--
---
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 orient
Im using object api not the graph. And it happens when i clear multiple
lists of nested objects, like, match.getGoals.clear then I call
match.getGoals.addAll(newGoalsList) i see in the errors log orientdb
exception regarding not found records #27.6765 some id. And then the
timeout exception lock.
i also was getting this. It seems when you do thing using the graphdb it
cause problems
My queries and updates where like this
select * from groups where @rid = #12:3
I change them to this
select * from #12:3
I had updates like this
update table set mfield = 12 where @rid = #14:4
i change
