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!

db_ad
10 years ago
It was a bug from the API which is being solved

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
  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
    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
  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.
  - 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' ?
db_ad
Guide
10 years ago
It was a bug from the API which is being solved
- LauraSch
  Contributor
  8 years ago
  Hi,
  
  Did this bug ever get resolved in the API? I'm currently having the same issues.
  
  Thanks!
  - 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.