Thanks. I changed my code to identify type relying on clusterid instead of 
internal class name.
Pawel

On Monday, March 3, 2014 1:32:09 PM UTC+1, Fabrizio Fortino wrote:
>
> AFAIK the class name has been removed from documents. Take a look at this 
> issue https://github.com/orientechnologies/orientdb/issues/1818
>
> On Saturday, March 1, 2014 5:22:02 PM UTC, Pawel K. wrote:
>>
>> Hi guys,
>>
>> Using recent SNAPSHOT I can't identify properly class name in binary 
>> protocol.
>>
>> Previously I could send class name in following format
>>
>>
>> Actor@FirstName:"Kristen",LastName:"Stewart",MainPicture:,out_AreFriends:<#15:0>
>>
>> Now it leads to the creation of field named Actor@FirstName which is of 
>> course unwanted behaviuor.
>>
>> Did something being changed in serialization to string regarding class 
>> name?
>>
>> Best regards,
>> Pawel
>>
>>

-- 

--- 
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.

Reply via email to