Nikul Ukani

Try `graph.ofriends.query().order_by(OFriends.aux_id, reverse=True).limit(1).first().aux_id`

try `traverse outE('has_component'), inV() from ...` or simply `traverse out('has_component') from ...` if you are only interested in the Nodes and not the Relationships.

Look at the comment https://github.com/mogui/pyorient/issues/274#issuecomment-481025944 for an example of how to use the OGM broker to query.

The CSV serializer seems to fail with the roundtrip encoding of dates (atleast with OrientDB 2.2.5). I will write a script that tests both roundtrip (with possibly different timezones) and...

It seems using UTC for serializing/deserializing seems to work for all scenarios. Check the output https://goo.gl/c1LuzG generated by the script https://goo.gl/ViLtk8 The script was ran against pyorient and pyorient_native develop...

I am just testing the encoding and decoding of dates with that script. Datetimes are considered a different data type by OrientDB and they are handled correctly by both CSV...

Just went through some code on the OrientDB side to see how they handle dates and realized that the serialization/deserialization behavior for Binary and CSV is different on the server...

The graph.create_edge command expects objects that are subclasses of vertex, and not raw OrientRecords. For your code, one way to use create_edge would be along the following lines ```python graph.create_edge(Friend,...

You can use the OGM with binary deserialization if you are using the develop branch of pyorient and have pyorient_native installed `from pyorient.ogm import Graph, Config` `from pyorient.serializations import OrientSerialization`...

Can you post the output of maven -version and java -version?