Add parser support for <explicit table>

[KamilaBorowska]

SQL translator incorrectly translates this query:

TABLE foo;

TABLE is a PostgreSQL-specific command.

Parser output:

Unexpected content after end of field input: [1:7] TABLE [*]foo;

[lukaseder]

Thanks a lot for your suggestion.

The <explicit table> is a possible <query primary> (and thus <query expression body>) according to the SQL standard, not just according to PostgreSQL. It's not a command on its own, it's just one of many things you can put in a query. For example, you can do this:

create table t as select 1 a;
table t union all table t;

It would definitely make sense to support it, both

• in jOOQ (will be implemented later)
• in the parser.

I could have sworn we already had an issue for this, but I cannot seem to find it...

[lukaseder]

Parser support will be added to jOOQ 3.15. API support is more tricky, and probably not very urgent (similar to VALUES constructor support, which is implemented in the parser, but not in the API).