add support for parsing "create domain" statement

[cvng]

What kind of change does this PR introduce?

Feature: try to add support for "create domain" statement as requested in #51

What is the current behavior?

Parser panics:

could not find node for token Token { kind: Create, text: "CREATE", span: 0..6, token_type: ReservedKeyword } at depth 1

What is the new behavior?

Parser returns:

  [email protected]
    [email protected] "CREATE"
    [email protected] " "
    [email protected] "DOMAIN"
    [email protected] " "
    [email protected] "us_postal_code"
    [email protected] " "
    [email protected] "AS"
    [email protected] " "
    [email protected]
      [email protected] "TEXT"
    [email protected] ";"

Additional context

Not sure of what exactly should go in the CreateDomainStmt branch, but I have tried with these variations and it worked:

CREATE DOMAIN name [ AS ] data_type [ constraint [ ... ] ]

[psteinroe]

thanks for the contribution! can you check the node output with debug logs enabled and ensure that the properties match their nodes?

also, what would help you in figuring this out faster? I think we can improve here.

[cvng]

Got it, I have removed the extra token, thanks!

For the As token (which is optional), it has no effect under the TypeName node, so I had to keep it under the CreateDomainStmt node or the parser still panics with:

could not find node for token Token { kind: As, text: "AS", span: 29..31, token_type: ReservedKeyword } at depth 2

As a side-note: TypeName node starts at location: Some(32) so maybe this is why?

1: Node {
    kind: TypeName,
    depth: 1,
    properties: [
        TokenProperty {
            value: Some(
                "text",
            ),
            kind: None,
        },
    ],
    location: Some(
        32,
    ),
},

[psteinroe]

lgtm! once you merge main tests should pass too :)