QueryExtra

[inzanez]

@fMeow Did you have any plans on how to implement retrieval of QueyExtra data? I would like to implement that asap, as I need it.

I was just scanning through the code and think that extending the existing functions:

• aql_fetch_all
• aql_query

might be hard. But it could still be convenient to have something integrated. How about adding new functions:

• aql_fetch_all_extra
• aql_query_extra

which would return QueryExtra data in addition to the results.

[inzanez]

Any update on this one? If you are not implementing anything already I would get started with this.

[fMeow]

Thank you for your kind suggetion.

I haven't used this feature and I fail to find QueryExtra in the arangodb document. Could you please give a link?

[inzanez]

It‘s not a particular function. It‘s the ‚extra‘ information from the query response. I think only ‚results‘ are parsed right now, the rest is ignored. For instance, the 'total_count' etc. would be interesting.

[fMeow]

This is already inplemented. You can use aql_query_batch and aql_next_batch to get a Cursor which contains QueryExtra. See aql_fetch_all for usage.

aql_fetch_all, aql_query and etc are handy functions for a quick retrieval, which is actually a wrapper around aql_query_batch and aql_next_batch. ArangoDB actually returns a cursor, which contains all the extra information.

The reason of neglecting QueryExtra is that it may change across Cursor. So the end result is a list of QueryExtra, which is not ergonomic to me.