Query: No keywords (like IN or WITH) allowed between non-text where string-like values are expected.

Created by: Quazgar

The query

FIND file which is stored at /SimulationData/2016_single/2018-01-10/in0.3out6open120close150vgate0.13etagate0.001lamba0/**

results in this beautiful error:

AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.AtemptingFullContext conflict in query. Please report this with a bug ticket.Ambiguity conflict in query. Please report this with a bug ticket.mismatched input 'in' expecting {<EOF>, WITH, WHICH, STAR, DOT, ESC_REGEXP_END, ESC_STAR, ESC_BS, '-', ':', NUM, TXT}

This is especially bad as it cannot be fixed by quoting the path (see #30 (closed)).

Imported comments:

By Timm Fitschen on 2021-02-18T16:12:37.715Z

mentioned in commit 3f958668

By Florian Spreckelsen on 2021-02-18T16:12:37.712Z

mentioned in commit b5e10adf

By Timm Fitschen on 2021-02-17T16:44:31.749Z

mentioned in commit caosdb-pyinttest@aa3cd17ddc40ac67d26b29401be380e8087ed696

By Timm Fitschen on 2021-02-17T13:58:01.593Z

mentioned in merge request !78 (merged)

By Quazgar on 2020-06-16T09:38:45.050Z

An even simpler query would be FIND foo with someprop = foo1in2bar. This seems to happen everywhere where a string-like value is expected.

By Quazgar on 2020-06-16T09:36:42.186Z

changed title from {-No "in[0-9]" dots in file path allowed-} to Query: No keywords (like IN or WITH) allowed between non-text where string-like values are expected.

By Quazgar on 2020-06-15T15:20:30.286Z

unassigned @timm.fitschen

By Quazgar on 2020-06-15T15:20:30.147Z

Failure during test:

line 1:35 mismatched input 'in' expecting {<EOF>, WITH, WHICH, STAR, DOT, ESC_REGEXP_END, ESC_STAR, ESC_BS, '-', ':', NUM, TXT}
(cq FIND (role FILE) (entity_filter (which_exp WHICH) (filter_expression (storedat IS STORED AT (location / data /)))) in 0 . foo)
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.322 s <<< FAILURE! - in caosdb.server.query.TestCQL
[ERROR] testIssue31(caosdb.server.query.TestCQL)  Time elapsed: 0.09 s  <<< FAILURE!
java.lang.AssertionError: expected:<4> but was:<7>
at caosdb.server.query.TestCQL.testIssue31(TestCQL.java:6287)

By Quazgar on 2020-06-15T15:04:12.125Z

mentioned in commit d6efccea

By Timm Fitschen on 2019-11-20T12:52:14.482Z

On Hold

check again after #30 (closed) has been fixed

By Timm Fitschen on 2019-09-11T15:02:20.982Z

changed due date to September 18, 2019

By Timm Fitschen on 2019-09-03T06:25:51.973Z

changed due date to September 11, 2019

By Quazgar on 2019-08-30T08:55:18.413Z

Possible test case for the TestCQL.java unit test class:

String issue31 = "FIND FILE WHICH IS STORED AT /foo/in0.dat";

By Timm Fitschen on 2019-08-30T06:33:38.115Z

changed due date to September 04, 2019

By Timm Fitschen on 2019-08-30T06:33:32.788Z

assigned to @timm.fitschen

By Quazgar on 2019-08-13T14:14:50.479Z

changed title from No dots in file path allowed to No {+"in[0-9]" +}dots in file path allowed

By Quazgar on 2019-08-13T09:58:12.786Z

marked this issue as related to #27 (closed)

By Quazgar on 2019-08-13T09:57:46.604Z

Possibly related to #27 (closed).

By Quazgar on 2019-08-04T14:11:37.088Z

changed the description

By Henrik tom Woerden on 2019-08-04T14:11:37 (imported from GitLab project)