By the way, I have an old comment on "explain" command - in the 
documentation (http://orientdb.com/docs/2.1/SQL-Explain.html) it is 
said that elapsed time measured in seconds with nanoseconds precision. 
I believe what we have in "elapsed" answer are milliseconds, actually (with 
6 decimal digits for nanoseconds).
Am I right?

On Friday, March 11, 2016 at 2:03:40 PM UTC+5, Enrico Risa wrote:
>
> For now if you want to know the core query timing  the only way is with 
> explain.
>
> If you do a normal query Studio uses OrientDB http protocol that gives 
> back only the results
> set. So the execution time is taken client side.
>
> 2016-03-11 9:18 GMT+01:00 'scott molinari' via OrientDB <
> [email protected] <javascript:>>:
>
>> Ahh...ok. Thanks for the answer. I was hoping it would be that. 
>>
>> Would be cool, if the core query timing on the server could be shown too. 
>>
>> Scott
>>
>> -- 
>>
>> --- 
>> 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/d/optout.
>>
>
>

-- 

--- 
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/d/optout.

Reply via email to