[BUG] JSQLParser Version : 5.1 RDBMS : PostgreSQL 10 mix the JSON and relational operators, it outputs the wrong AST and sql. #2163

Activity

1. hijackworld commented on Feb 11, 2025

   

   hijackworld

   on Feb 11, 2025

   Author

   More actions

   BTW
   if we parse the new sql SELECT * FROM t WHERE js#>>'{a,b,1}' <> 'bar'
   JSQLParser will recognize it as a wrong Bitwise operation in the AST:
   the collumn name is js#, and the operator is >>.
2. manticore-projects commented on Feb 11, 2025

   

   manticore-projects

   on Feb 11, 2025

   Last edited by manticore-projects

   Contributor

   More actions

   the collumn name is js#, and the operator is >>

   In this case you will need to quote the column name like "js#" since it interferes with the JSON operator #>>.

   SQL Text
    └─Statements: statement.select.PlainSelect
       ├─selectItems: statement.select.SelectItem
       │  └─AllColumns: *
       ├─Table: t
       └─where: expression.operators.relational.NotEqualsTo
          ├─leftExpression: expression.operators.arithmetic.BitwiseRightShift
          │  ├─Column: "js#"
          │  └─StringValue: '{a,b,1}'
          └─StringValue: 'bar'
   
3. hijackworld commented on Feb 11, 2025

   

   hijackworld

   on Feb 11, 2025

   Last edited by hijackworld

   Author

   More actions

   thanks.
   what about the issue of the wrong priority?
   js #>> ('{a,b,1}' <> 'bar')

   in fact, what we need is: (js #>> '{a,b,1}') <> 'bar', just like PG does.

   we parse the original sql by JSQLParser 4.9, and it works well.
   it seems like a bug for version 5.1 .
4. manticore-projects commented on Feb 11, 2025

   

   manticore-projects

   on Feb 11, 2025

   Contributor

   More actions

   what about the issue of the wrong priority?

   Adding brackets for clarity may be your best instant solution.

   SQL Text
    └─Statements: statement.select.PlainSelect
       ├─selectItems: statement.select.SelectItem
       │  └─AllColumns: *
       ├─Table: t
       └─where: expression.operators.relational.NotEqualsTo
          ├─ParenthesedExpressionList: (js#>>'{a,b,1}')
          └─StringValue: 'bar'
   
   
5. fudianchn commented on Aug 22, 2026

   

   fudianchn

   on Aug 22, 2026

   Contributor

   More actions

   Verified on current master (a5765f3): select * from t where js #>> '{a,b,1}' <> 'bar' now parses with the expected precedence: the WHERE clause is NotEqualsTo(JsonExpression(js #>> '{a,b,1}'), 'bar'). The deparser output also keeps the spaces: SELECT * FROM t WHERE js #>> '{a,b,1}' <> 'bar'. Both reported errors are resolved. Can this be closed?

   👍React with 👍1Reacted by manticore-projects
6. manticore-projects

   closed this as completedon Sep 11, 2026