Michele Rastelli

I mean specifically `writeRaw()`, in order to append an already properly encoded byte sequence. I would like to achieve the same behavior of `writeRaw(String|char[]|SerializableString)` for binary dataformats. Of course not...

Thanks! I think it would be even better adding new methods to `com.fasterxml.jackson.core.JsonGenerator`, e.g. `writeRaw((byte[]|InputStream) data)`. This would allow further enhancements at databind level by adding support for `byte[]` value...

Sounds good to me, thanks for sharing! I will draft a PR as I find time. Should we move the discussion to `jackson-core` project in order to offer better visibility...

I think this is not driver related: if the db will support in the future binary fields/objects the driver will support them as well. Currently you can achieve something similar...

Thanks for clarifying, in general I like the idea. I would proceed defining a specification which will be then implemented by all the drivers.

You are right, this is unfortunately due to some legacy design decision. To work around it, you can manually create the requests to consume the cursor and execute them by...

Here is an example showing how to consume a cursor in a non-blocking way using `com.arangodb.async.ArangoDBAsync#execute`: https://gist.github.com/rashtao/513172e4a001f6f1708ed0cbb3a895bf

This should be because the cursor expired on the server side. To work around it you can increase cursor's TTL, see https://arangodb.github.io/spring-data/javadoc-3_7/com/arangodb/springframework/annotation/QueryOptions.html#ttl-- and https://www.arangodb.com/docs/stable/http/aql-query-cursor-accessing-cursors.html

Closing for now, please reopen in case of further problems.

You can enable debug level for such logger adding the following to your `logback.xml`: ```xml ``` Additionally you might want to filter the logged rows using Logback filters: http://logback.qos.ch/manual/filters.html