Sorry Andrey, This was definitely my fault. The client application was pointing at 1.7-RC1 libs. I have changed it to 1.7-rc2-SNAPSHOT and it works as expected.
Thanks a lot, F. On Thursday, February 20, 2014 2:59:28 PM UTC, Andrey Lomakin wrote: > > If you updated everything could you send me your database ? > > > On Thu, Feb 20, 2014 at 4:58 PM, Andrey Lomakin > <[email protected]<javascript:> > > wrote: > >> 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 >> <[email protected]<javascript:> >> > wrote: >> >>> Yes, it helps very much. >>> >>> >>> On Thu, Feb 20, 2014 at 1:32 PM, Fabrizio Fortino >>> <[email protected]<javascript:> >>> > wrote: >>> >>>> 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 = graph.addVertex("class:V1"); >>>> >>>> Map<String, Object> properties = new HashMap<String, Object>(); >>>> properties.put("ID", "100001"); >>>> properties.put("LONG_NAME", "bleeding extra long name"); >>>> properties.put("ADDRESS", "123 A Street San Francisco, Californa, >>>> United States"); >>>> properties.put("CNTRY_OF_DOMICIL", "US"); >>>> >>>> >>>> v1.setProperties(properties); >>>> >>>> graph.commit(); >>>> >>>> graph.shutdown(); >>>> >>>> >>>> Querying the class V1 the field CNTRY_OF_DOMICIL is stored as V1@ >>>> CNTRY_OF_DOMICIL >>>> >>>> Hope it helps, >>>> F. >>>> >>>> On Thursday, February 20, 2014 11:19:49 AM UTC, Andrey Lomakin wrote: >>>> >>>>> BTW do you use remote or embedded storage ? >>>>> >>>>> >>>>> On Thu, Feb 20, 2014 at 1:17 PM, Andrey Lomakin >>>>> <[email protected]>wrote: >>>>> >>>>>> 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 <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> Hi, >>>>>>> Luca you are right I will commit during 15 min. >>>>>>> >>>>>>> >>>>>>> On Thu, Feb 20, 2014 at 12:44 PM, Luca Garulli <[email protected]>wrote: >>>>>>> >>>>>>>> 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 >>>>>>>> <[email protected]>wrote: >>>>>>>> >>>>>>>>> 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 vertex (VertexA) with related edges >>>>>>>>>> pointing to other vertexes(VertexB). To create and edge I use the >>>>>>>>>> following >>>>>>>>>> code: >>>>>>>>>> >>>>>>>>>> graph.addEdge(null, vA, vB, "has"); >>>>>>>>>> >>>>>>>>>> As you can see I use the label "has". When I browse VertexA I >>>>>>>>>> noticed that for some records the edge property is name is >>>>>>>>>> VertexA@out_has >>>>>>>>>> instead of out_has . >>>>>>>>>> >>>>>>>>>> The same code was working with 1.7RC1, so I think something >>>>>>>>>> happened in the latest commits. >>>>>>>>>> >>>>>>>>>> Any idea? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Fabrizio >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>> >>>>>>>>> --- >>>>>>>>> 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/groups/opt_out. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> --- >>>>>>>> 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/groups/opt_out. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Andrey Lomakin. >>>>>>> >>>>>>> Orient Technologies >>>>>>> the Company behind OrientDB >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Andrey Lomakin. >>>>>> >>>>>> Orient Technologies >>>>>> the Company behind OrientDB >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Andrey Lomakin. >>>>> >>>>> Orient Technologies >>>>> the Company behind OrientDB >>>>> >>>>> -- >>>> >>>> --- >>>> 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/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Andrey Lomakin. >>> >>> Orient Technologies >>> the Company behind OrientDB >>> >>> >> >> >> -- >> Best regards, >> Andrey Lomakin. >> >> Orient Technologies >> the Company behind OrientDB >> >> > > > -- > Best regards, > Andrey Lomakin. > > Orient Technologies > the Company behind OrientDB > > -- --- 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/groups/opt_out.
