Forum Discussion

db_ad's avatar
db_ad
Guide
10 years ago
Solved

Liql unknown error

Given this:

https://community.lithium.com/t5/Community-API-v2/Message-resource/ta-p/113091​

SELECT * FROM messages WHERE depth = 0 AND conversation.solved = true

That's an example query from the documentation, when executed on our environments it returns:

{
"status": "error",
"message": "invalid query syntax for SELECT * FROM messages WHERE depth",
"data": {
"type": "error_data",
"code": 603,
"developer_message": "",
"more_info": ""
},
"metadata": {}
}

Is something being done wrong there?

 

Thanks!

16 Replies

Sort By
Show More
  • db_ad's avatar
    db_ad
    Guide
    10 years ago
    Both fail with the same error as my first one:


    {
    "status": "error",
    "message": "invalid query syntax for SELECT conversation.solved FROM messages WHERE depth",
    "data": {
    "type": "error_data",
    "code": 603,
    "developer_message": "",
    "more_info": ""
    },
    "metadata": {}
    }?
  • OlivierS's avatar
    OlivierS
    Lithium Alumni (Retired)
    10 years ago

    db_ad I think the depth=0 is the problem, as the query below works fine on your dev instance:

     

    SELECT conversation.solved FROM messages WHERE depth !=0

     

    I can't understand how you could have messages with a depth of 1 and more without having any at depth 0 ... It might be worth checking with support on this one!

     

    depth   How many levels away from the topic message the message appears in the conversation thread. Zero (0) indicates that the message is topic message.; 1 indicates a reply; 2 indicates a reply to a reply, and so on. int
  • db_ad's avatar
    db_ad
    Guide
    10 years ago
    I'm in contact with support.


    First place, seems that all the query must be URL encoded. Anyway, there're certain queries that are not working as they should and they're investigating


    Thank you :-)

    ?
  • db_ad's avatar
    db_ad
    Guide
    10 years ago

    It was a bug from the API which is being solved

  • LauraSch's avatar
    LauraSch
    Contributor
    8 years ago

    Hi,

     

    Did this bug ever get resolved in the API? I'm currently having the same issues.

     

    Thanks!

  • VikasB's avatar
    VikasB
    Boss
    8 years ago

    Hi LauraSch  It seems the instance specific issue. It's working fine at my end. You can raise a ticket to support team.