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
  • VarunGrazitti's avatar
    VarunGrazitti
    Boss
    10 years ago

    db_ad - This works fine for me. Not sure but do you have data on your stage at the moment? Try this call by removing 'depth = 0'

  • db_ad's avatar
    db_ad
    Guide
    10 years ago

    That doesn't work also, getting similar error.

     

    Other queries, for example "SELECT id, topics.count(*), messages.count(*), views FROM boards where id in ('123,124') ORDER BY messages.count(*) DESC" do work, there's data available

     

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

  • VarunGrazitti's avatar
    VarunGrazitti
    Boss
    10 years ago
    db_ad - Run this command to see if your instance is working fine, else contact Li support.

    SELECT * FROM messages
  • OlivierS's avatar
    OlivierS
    Lithium Alumni (Retired)
    10 years ago

    db_ad working fine for me too.

     

    As well as checking if you have any data, try entering the query manually, so you're sure there isn't any hidden characters causing issues.

     

    2015-03-24_1124.png

  • db_ad's avatar
    db_ad
    Guide
    10 years ago
    SELECT * FROM messages (using valid access token)


    {
    "status": "error",
    "message": "An unexpected error occurred.",
    "data": {
    "type": "error_data",
    "code": 301,
    "developer_message": "",
    "more_info": ""
    },
    "metadata": {}
    }?
  • OlivierS's avatar
    OlivierS
    Lithium Alumni (Retired)
    10 years ago

    db_ad 

     

    Also, what does 

     

    SELECT conversation.solved FROM messages

     

    returns?

     

    If you have data, have you got any with a value 'true' ?

     

    2015-03-24_1129.png

     

     

  • OlivierS's avatar
    OlivierS
    Lithium Alumni (Retired)
    10 years ago

    db_ad is your instance up and running? Could you PM me your url. If it's stage I could have a quick look at it.

  • db_ad's avatar
    db_ad
    Guide
    10 years ago
    ?@OlivierS SELECT conversation.solved FROM messages returns 25 results:


    {
    "status": "success",
    "message": "",
    "http_code": 200,
    "data": {
    "type": "messages",
    "list_item_type": "message",
    "size": 25,
    "items": [
    {
    "type": "message",
    "conversation": {
    "type": "conversation",
    "solved": true
    }
    },
    {
    "type": "message",
    "conversation": {
    "type": "conversation",
    "solved": true
    }
    },?

    ........?
  • OlivierS's avatar
    OlivierS
    Lithium Alumni (Retired)
    10 years ago

    db_ad 

     

    How about this one:

     

    SELECT conversation.solved FROM messages WHERE depth = 0

     

    And if it works, that one:

     

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