Greetings,

Thank you for your bug report.

May I please clarify with you the next questions so that we could find the exact reason for the issue?

Here they are:

     1) Is the issue reproduced after you save a SOQL query file?

     2) Is the message that you get a warning or an error?

     3) Do you get results after executing your SOQL query in the SOQL query builder? If no, does a header of the table appear in the results section?

If the issue is reproduced after you save your SOQL query, please send us a bug report directly from the IDE - you can find the option for this in the menu Help -> Report a Bug, please enable the 'Attach Log File' checkbox and out your email.

All this information will help us greatly to solve the issue.

Thank you,

Kate

Hello,

yes it's a warning message, but now I see results, maybe I didn't save the file, I don't know what happens but I can't reproduce this issue, it seems that's OK now!

Thank you.

Hi.

Thank you for your response with the update.

I'm glad that now everything work properly.

We will investigate the behaviour for unsaved files and will check if any other reasons can cause this.

If you would have any pther questions, please let me know. I will be happy to help you.

Regards,

Kate

Hi Kate,

I have been seeing this issue as well.  The message is just a warning, so the results still load.  In my case, I have the error/warning panel auto-hidden at the bottom, so every time it pops up and covers the SOQL results so it seems like the query didn't run.  Here is an example query and the resulting warning message:

SELECT Id FROM Account WHERE CreatedDate = 2017-11-09

Warning 60 C:\Users\... Message: mismatched input '-11' expecting <EOF>, position 44 1 1

EDIT: CreatedDate on Account is actually a date/time field, so my query above doesn't work, but you get the idea.  I just tested with a date/time value (2017-11-09T00:00:00Z) and there is no warning message.

Hi Mfrizzell,

Thank you for sharing this additional example and for your post.

We will include this information to our investigation. Looks like the reason for appearing the warning message is related exactly to date/time format of an object field and a specified format of a date in a query.

Our developers will make the necessary changes to solve this issue.

Thank you for your collaboration.

Regards,

Kate