feat: add support for type name

[cvng]

What kind of change does this PR introduce?

add support for "some" typename

What is the current behavior?

parser panics

What is the new behavior?

parser returns

Additional context

as I understands it, the case that causes panics are:

• multi-word type name, eg: timestamp with time zone
• and interval options, eg: hour to second(3)

single-word type name, looks ok but I will have to double-check. cc @psteinroe

[psteinroe]

For the type names, you can extend the alias definition. I think it's defined directly in the parser code.

[cvng]

For the type names, you can extend the alias definition. I think it's defined directly in the parser code.

OK, after going back in the git history, it looks like the original parser panics was fixed, so not sure if this if required anymore?

the original error and the failing case:

could not find node for token Token { kind: To, text: "to", span: 98..100, token_type: ReservedKeyword } at depth 4

CREATE TABLE IF NOT EXISTS distributors (name varchar(40) DEFAULT 'Luso Films', len interval hour to second(3), name varchar(40) DEFAULT 'Luso Films', did int DEFAULT nextval('distributors_serial'), stamp timestamp DEFAULT now() NOT NULL, stamptz timestamp with time zone, "time" time NOT NULL, timetz time with time zone, CONSTRAINT name_len PRIMARY KEY (name, len));
                                                                                                  ^

I was about to implement this https://github.com/pganalyze/libpg_query/blob/16-latest/src/postgres_deparse.c#L3879

EDIT: I had the wrong base reference, the parser still panics, I will try Alias as suggested

[cvng]

base case added in 3aba5fb

[psteinroe]

lgtm, thanks!

[cvng]

TODO: add other fields from intervaltypmodout