Re: [orientdb] Error on parsing query Found invalid ) character

Seems to be fixed in 2.1.11. Thank you ! Le lundi 8 février 2016 09:12:10 UTC+1, Alain a écrit : > > Hi, > Months after reporting this bug, there is still no fix published. > The latest version (2.1.10) gives the following error: >

Re: [orientdb] Error on parsing query Found invalid ) character

Hi, Months after reporting this bug, there is still no fix published. The latest version (2.1.10) gives the following error: com.orientechnologies.orient.core.exception.OCommandExecutionException: Error on execution of command: Please tell us if we can hope for a fix or we should look for a

Re: [orientdb] Error on parsing query Found invalid ) character

Hi Luigi, Any news related to this bug ? Thanks, Alain Le mardi 17 novembre 2015 00:42:54 UTC+1, Luigi Dell'Aquila a écrit : > > Hi Alain, > > a few days ago I fixed an issue that can be related to this, any chance to > try 2.1.x branch? > > Thanks > > Luigi > > > 2015-11-16 15:17 GMT+01:00

Re: [orientdb] Error on parsing query Found invalid ) character

I suppose the fix was not included in version 2.1.6 (I still get the error with this version) ? Le mardi 17 novembre 2015 08:54:49 UTC+1, Alain a écrit : > > Hi Luigi, > After a quick test, it seems the bug is fixed in the latest snapshot. I'm > waiting for the next official release in order

Re: [orientdb] Error on parsing query Found invalid ) character

Fyi, the bug is still existing in 2.1.5. Any plan on working on it soon ? Thanks in advance. Le mercredi 14 octobre 2015 12:25:19 UTC+2, Alain a écrit : > > Just fyi, I updated the bug with the result of my tests with version 2.1.3 > and 2.1.4. The bug is still there (obviously since the bug is

Re: [orientdb] Error on parsing query Found invalid ) character

Hi Alain, a few days ago I fixed an issue that can be related to this, any chance to try 2.1.x branch? Thanks Luigi 2015-11-16 15:17 GMT+01:00 Alain : > Fyi, the bug is still existing in 2.1.5. Any plan on working on it soon ? > > Thanks in advance. > > > Le

Re: [orientdb] Error on parsing query Found invalid ) character

Hi Luigi, After a quick test, it seems the bug is fixed in the latest snapshot. I'm waiting for the next official release in order to run more comprehensive tests, but I feel confident. Thank you for your feedback ! Alain Le mardi 17 novembre 2015 00:42:54 UTC+1, Luigi Dell'Aquila a écrit : >

Re: [orientdb] Error on parsing query Found invalid ) character

Just fyi, I updated the bug with the result of my tests with version 2.1.3 and 2.1.4. The bug is still there (obviously since the bug is still opened). Le vendredi 2 octobre 2015 11:01:47 UTC+2, Luigi Dell'Aquila a écrit : > > Hi Alain, > > thanks a lot, I'll check it soon > > Thanks > > Luigi

Re: [orientdb] Error on parsing query Found invalid ) character

Hi Luigi, I also noticed the problem and appended the bug https://github.com/orientechnologies/orientdb/issues/4996 with my case. Thank you, Le jeudi 1 octobre 2015 06:58:54 UTC+2, Luigi Dell'Aquila a écrit : > > Hi Ravinder, > > I lost track of this, was it reported in the issue tracker? > If

Re: [orientdb] Error on parsing query Found invalid ) character

Hi Alain, thanks a lot, I'll check it soon Thanks Luigi 2015-10-02 10:44 GMT+02:00 Alain : > Hi Luigi, > I also noticed the problem and appended the bug > https://github.com/orientechnologies/orientdb/issues/4996 with my case. > > Thank you, > > > Le jeudi 1 octobre

Re: [orientdb] Error on parsing query Found invalid ) character

Hi Ravinder, I lost track of this, was it reported in the issue tracker? If not, could you please create an issue specifying the OrientDB version where it still happens? Thanks Luigi 2015-09-30 19:14 GMT+02:00 Ravinder Payal : > is the bug shorted out is that

Re: [orientdb] Error on parsing query Found invalid ) character

is the bug shorted out is that exist even now i am also getting the same problem. The problem may occur when any user added parenthesis in their post that will be stored in orient db On Monday, March 24, 2014 at 8:54:35 PM UTC+5:30, Andrey Lomakin wrote: > > Hi, > > I am working on this. > >

Re: [orientdb] Error on parsing query Found invalid ) character

I have the same problem looking for ) character in a text by gremlin in REST on 161 version. g.V('@class', 'Comment').filter { it.text.contains())}.text this is the full error: System.Exception: DB Error:InternalServerError.

Re: [orientdb] Error on parsing query Found invalid ) character

Hi, I am working on this. On Mon, Mar 24, 2014 at 12:40 PM, Diego Martelli diego.marte...@gmail.comwrote: I have the same problem looking for ) character in a text by gremlin in REST on 161 version. g.V('@class', 'Comment').filter { it.text.contains())}.text this is the full error:

Re: [orientdb] Error on parsing query Found invalid ) character

What query? Lvc@ On 18 February 2014 14:25, Shishya prabha...@gmail.com wrote: Luca, even though I add a space after the ), I get the same error. Any workarounds please regards On Thursday, October 11, 2012 5:00:59 PM UTC+5:30, Meerkatzenwildschwein wrote: I've changed this as you

Re: [orientdb] Error on parsing query Found invalid ) character

This query works fine in console, but fails in bulk INSERT INTO US_simplified_data (patent_id, national_class, title, status, time_stamp, kind, iso_date, ipc_version, inventors, international_class, further_national_class, further_international_class, date, country, citations, assignees,

Re: [orientdb] Error on parsing query Found invalid ) character

Hi, sorry it's pretty unreadeable. You should check if any ) is missing somewhere. Lvc@ On 18 February 2014 14:32, prabhat prabha...@gmail.com wrote: This query works fine in console, but fails in bulk INSERT INTO US_simplified_data (patent_id, national_class, title, status, time_stamp,

Re: [orientdb] Error on parsing query Found invalid ) character

No, Its all correct actually. There is all correct syntaxes. It works fine in studio. But gives this error in massiveinsert. Prabhat Kumar Singh On Tue, Feb 18, 2014 at 7:29 PM, Luca Garulli l.garu...@gmail.com wrote: Hi, sorry it's pretty unreadeable. You should check if any ) is missing