Hi Riccardo, It is rather a lack of optimization.
In such case query engine will go over all records and check class, while this is completely unnecessary because we have we have this information in metadata. The query uses grouping by class name. So we need to create an optimization for group by that is definitely possible but not easy to do in a current design. And optimization will fit only for this particular type of query. So in my opinion it is just don't worth it, it is much easier to use API for such thing. Best regards, Artem Orobets * Orient Technologiesthe Company behind OrientDB* 2014-05-30 10:14 GMT+03:00 Riccardo Tasso <[email protected]>: > > 2014-05-30 9:11 GMT+02:00 Artem Orobets <[email protected]>: > > Doing that from SQL is not efficient. >> > > It's a pity, do you consider it a bug? > > Riccardo > > -- > > --- > 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. > -- --- 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.
