Greetings @ssteinhauser

I will look into this tomorrow morning and find a solution (its evening here already).

I believe, you need to define you own Identified and QuotedIdentifier without any double dots.
Or we need to find a way to disable the double dots in the multipart table names (because it applies only for Sybase/SQLServer).

Basically, we can define another Feature like allowDoubleDotMultipartIdentifers and then make conditional LookAheads.
Or you define your own special RelObjectNames without allowing delimiters.

// table names seem to allow ":" delimiters, e.g. for Informix see #1134
ObjectNames RelObjectNames() : {
 String token = null;
 Token delimiter = null;
 List<String> data = new ArrayList<String>();
 List<String> delimiters = new ArrayList<String>();
} {
 token = RelObjectNameExt() { data.add(token); }
 (
 LOOKAHEAD (2) ( delimiter = "." | delimiter = ":" ) { delimiters.add(delimiter.image); } (( delimiter = "." | delimiter = ":" ) { data.add(null); delimiters.add(delimiter.image); })*
 token = RelObjectNameExt2() { data.add(token); }
 ) *
 { return new ObjectNames(data, delimiters); }
}
// column names do not allow ":" delimeters as those represent JSON `GET` operators
ObjectNames ColumnIdentifier() : {
 String token = null;
 Token delimiter = null;
 List<String> data = new ArrayList<String>();
 List<String> delimiters = new ArrayList<String>();
} {
 token = RelObjectNameExt() { data.add(token); }
 (
 LOOKAHEAD (2) ( delimiter = "." ) { delimiters.add(delimiter.image); } (( delimiter = "." ) { data.add(null); delimiters.add(delimiter.image); })*
 token = RelObjectNameExt2() { data.add(token); }
 ) *
 { return new ObjectNames(data, delimiters); }
}

Thank you for your quick reply @manticore-projects ,

can you please provide deeper insights of your thoughts?

Maybe I miss something, but up to my knowledge, introducing a feature flag or implementing my own RelObjectNames won't solve the issue. The pure existence and usage of the ".." token (no matter in which context) causes the unit tests to fail.
In the case of the IMPORT statement, I don't use it with RelObjectNames, it's being used in between <S_LONG> tokens.

If we would implement a feature flag, we would have to implement it that way, that the support of double dot multipart identifier is mutually exclusive with the IMPORT statement. Event then, I am not sure if it will work.

Good Morning @ssteinhauser.

Please see 9f51831 (sorry for committing directly, it was an accident).
I did not see any test for the IMPORT statement though, but it should work when setting the new feature allowSkippingPartsInIdentifiers to FALSE.

Good Morning @ssteinhauser .

I fully understand your concern, but .. is really a nightmare.

We could rework those RelObjectNames() productions and introduce the same tokens there, e.g. . .. or ... -- but I am honestly not very eager on this because it just works while ExaSol is a rather exotic usecase.

Right now, I would like to suggest to ignore that there can be whitespace in between. JSQLParser is meant to be a parser and not a validation tool.

Suggestion:

1. finish your work and ignore the possible whitespace between the dots
2. we merge in order to have a full working copy
3. we try to rework those productions and introduce proper tokens ., .., ...

I tried to work with Tokens in those two productions instead of chaining the . -- could not get it working in a reasonable time.