janjilek

+1 I have the same problem

Any news? It's really annoying bug and it's breaking my production env when sending twitter ids. It's just parsed in the wrong way and I am getting different number...

beginQuery event: { query: 'SELECT \* FROM gift WHERE uuid = :paramuuid0 LIMIT 1', mode: 'a', fetchPlan: 'in__:-2 out__:-2', limit: -1, token: undefined, language: undefined, class: 'com.orientechnologies.orient.core.sql.query.OSQLAsynchQuery', params: { params:...

hmm, when you plan to release fixed version? Parsing of json is really slow, because of useless list of edges on every request... I am more and more annoyed of...

Is the connection pool stable now? Few month ago, it was not working properly.

And rewrite it in raw query is not solution. I have hundreds of queries with sorting based on multiple attributes. I tested it also on 2.1.16 and same problem.

The problem is, that this query is generated by OrientJS query builder, so I cannot execute strict queries. And only solution is to rewrite every query without query builder =>...

.order('scheduleDate DESC, @rid DESC') generates (scheduleDate DESC, @rid DESC) and not scheduleDate DESC, @rid DESC

So the problem is in the driver. The solution is to remove if (utils.requiresParens(item)) { return '(' + item + ')'; } On line 809 in statement.js and return only...

I found workaround, use of array: .order(['scheduleDate DESC', '@rid DESC'])