Add bindings for pg_query_deparse_protobuf

[tomquist]

This exposes deparse functionality to node.js. As of this issue the recommended approach is to generate a protobuf message from the JSON parse tree. One blocking issue is that protobufjs doesn't honor the json_name attribute so it isn't able to parse the existing structure into a protobuf message. There's a PR to add this, however, this seems to be stale atm. In this PR I worked around this by directly pointing to the fork and generating a static JS model from it that I checked in. By checking in the model we could also point back to the original library, however, this makes updating the static model more cumbersome.

This pull request adds bindings for pg_query_deparse_protobuf to expose deparse functionality for Node.js. Currently, the recommended approach is to generate a protobuf message from the JSON parse tree, but the protobufjs library doesn't honor the json_name attribute, which blocks parsing of the existing structure into a protobuf message. Although a PR to address this issue is available here, it seems stale at the moment.

In this PR, a workaround has been implemented by directly pointing to the fork and generating a static JS model from it that is checked in. While checking in the model allows for pointing back to the original library, it also makes updating the static model more cumbersome.

[jgoux]

This is awesome, thanks for your contribution! 🥳

[benasher44]

@tomquist would https://github.com/protocolbuffers/protobuf-javascript work instead?

[pyramation]

oops, I deleted master and a few others in an attempt to have more clarity around branches, keep similar naming convention as libqg-query and it automatically closed this PR — re-opening :)

[pyramation]

Would love to breathe life back into this! I've actually written protobuf parsers from scratch (see https://github.com/cosmology-tech/telescope)

@tomquist was this PR working for you? If so, I can look into the details of the option json_name and handle this

I could also make a nice pipeline for updating the proto.js that gets generated. I'll take a deeper look :)

[pyramation]

$ npm run test

> [email protected] test
> mocha --timeout 5000



  Queries
    Sync Parsing
      ✓ should return a single-item parse result for common queries
      ✓ should support parsing multiple queries
      ✓ should not parse a bogus query
    Async parsing
      ✓ should return a promise resolving to same result
      ✓ should reject on bogus queries
    Deparsing
      ✓ async function should return a promise resolving to same SQL
      ✓ sync function should return a same SQL
      ✓ should reject on bogus input
    Fingerprint
      sync
        ✓ should not fingerprint a bogus query
        ✓ should fingerprint a query
      async
        ✓ should not fingerprint a bogus query
        ✓ should fingerprint a query

  PlPgSQL (async)
    ✓ should parse a function


  13 passing (12ms)

NOTE: yarn doesn't work with Tom's branch, but npm install does :)

I think this is a great start, I can work with this!

[pyramation]

I'm gonna merge this PR into a dev branch, and work on this!

[pyramation]

new PR #63