[orientdb] Re: edge problem with 1.7RC2

2014-02-20 Thread Fabrizio Fortino
Moreover, I noticed that a field named LONG_NAME has been stored has VertexA@LONG_NAME On Thursday, February 20, 2014 10:34:07 AM UTC, Fabrizio Fortino wrote: Hi guys, I have stumbled in a pretty critical project using the latest version from develop branch. I have a process that creates

Re: [orientdb] Re: edge problem with 1.7RC2

2014-02-20 Thread Luca Garulli
Hi Fabrizio, this seems related to last optimization about removing class from serialized record. @Andrey do you know why? Lvc@ On 20 February 2014 11:40, Fabrizio Fortino fabrizio.fort...@gmail.comwrote: Moreover, I noticed that a field named LONG_NAME has been stored has

Re: [orientdb] Re: edge problem with 1.7RC2

2014-02-20 Thread Andrey Lomakin
Hi Fabrizio, Could you send me your db in zipped format. I just looked at your message more carefully, so you add edge and read it just after add and you have given issue right ? On Thu, Feb 20, 2014 at 1:03 PM, Andrey Lomakin lomakin.and...@gmail.comwrote: Hi, Luca you are right I will

Re: [orientdb] Re: edge problem with 1.7RC2

2014-02-20 Thread Fabrizio Fortino
Hi Andrey, I have a plocal graph database. The client connects through the remote protocol. The database is pretty big. But I can easily reproduce the problem with the following code snippet: OrientGraph graph = new OrientGraph(remote:localhost/mydb, admin, admin); OrientVertex v1 =

Re: [orientdb] Re: edge problem with 1.7RC2

2014-02-20 Thread Andrey Lomakin
Hi Fabrizio, A question. Did you update only server libraries or client libraries too ? I am trying to reproduce it in different ways no luck. On Thu, Feb 20, 2014 at 1:37 PM, Andrey Lomakin lomakin.and...@gmail.comwrote: Yes, it helps very much. On Thu, Feb 20, 2014 at 1:32 PM, Fabrizio