Jay Pipes

We should include docstring comments for fields in the generated type definition and CRD definition output. This documentation is available in the aws-sdk-go's `doc.json` files (and I've included some of...

libunwind would be very useful to integrate into the `sqltoast::parse_context_t` struct, allowing the context to output debugging information including how many depths of recursion of a particular parsing function we're...

``` [jaypipes@uberbox _build]$ ./sqltoaster/sqltoaster --yaml "SELECT (SELECT d FROM t2 WHERE d.id = t2.id) AS d_id FROM t2" Syntax error. Expected to find one of ('*'|>) but found keyword[AS] SELECT...

There's a big TODO left in `parse_row_value_constructor()`: ```c++ if (cur_sym == SYMBOL_SELECT) { // TODO(jaypipes): handle subquery row value constructors return false; } ```

The has the following EBNF grammar: ``` ::= CAST AS ::= | NULL ::= | ```

The NULL constraint specifier is default for the `CREATE TABLE` statement, however we don't support it. We only support the standard `NOT NULL` constraint specifier: ``` jaypipes@uberbox:~/src/github.com/jaypipes/sqltoast/_build$ ./sqltoaster "create table...

There is now a `sqltoast::parse_options_t` switch that disables the construction of the `sqltoast::statement` objects if the caller doesn't want or need these objects. One reason the caller may not want...

Now that YAML output is shaping up nicely, I'd like to add support for DOT/graphviz output to sqltoaster. This would allow a machine-readable visual format.

Due the various things, including how the lexer's cursor is moved over time, sometimes the syntax errors produced when a parsing problem happens can be confusing. Por ejemplo: ``` ./sqltoaster/sqltoaster...

``` ::= | INTERSECT [ ALL ] [ ] ```