Hi, Yes this is correct, but we've an old bug on parameter parsing in nested sub-queries, so use this if you've a shallow query.
Lvc@ On 16 June 2014 16:51, Andreas Egloff <[email protected]> wrote: > A question on the effective use of prepared queries in a pooled/concurrent > environment. > > There does not seem to be an explicit pattern documented, but the examples > documented seem to show a pattern of creating a prepared query for each > execute > > query = new OSQLSynchQuery<ODocument>(queryString);result = > database.command(query).execute(params); > > Is this the correct interpretation, or is there a safe way to re-use > prepared queries in a threaded/pooled environment? Or is there caching > going on behind the scenes? > > Thanks, > Andi > > -- > > --- > 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.
