In many cases Blueprints queries are translated into SQL. If you want speed (with less compatibility) go with SQL ;-) The important is using Blueprints API and don't go underlying to get the ODatabaseDocumentTx instance.
Lvc@ On 15 July 2014 00:53, Andrey Kovalev <[email protected]> wrote: > Sorry, but I do not know ) > I saw somewhere in old posts developers recommended to go with Blueprints > in terms of beauty and compatibility of code. But the fastest approach is > sql. But probably I understood it in a wrong way. Developers should put > their opinion here. > > > On Monday, 14 July 2014 14:34:44 UTC+1, Tiziano Fortin wrote: >> >> Hi Andrey, >> >> now it works, but my mistake was in the wrong management in handling null >> cases. >> >> However, what is the best way to perform a select like this? >> > -- > > --- > 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.
