sql-parser VS POCO

Hi HN-

This was built by our former intern @akubecka. There are lots of good SQL parsers out there, including things like hyrise (https://github.com/hyrise/sql-parser)but we needed something that would let us edit the parsed SQL and then replay the changed version. Couldn't find that so we decided to build.

We figured others must sometimes have the same need. Alex agreed to maintain it as an open source project, so CTM agreed to make it available under the MIT license.

You can also look into Poco https://pocoproject.org/

I can't say enough good stuff about POCO for this type of work - when I first got my teams using it we used to joke that POCO was what Boost wants to be when it grows up. And nlohmann/json - cracking library for working with JSON in C++.

We use https://github.com/pocoproject/poco in most projects, very easy to set up a http listener

Did someone used Poco's Net Library to create a Rest Api? Poco Project

But CLion is so slow. Tested with Poco C++ standard build (https://pocoproject.org/). Moving around with Go To Definition takes sometimes up to 20 seconds if file is first touched. Using 'back' and 'forward' delays for 1-2 seconds.

Yes, you need NetSSL - take a look at find_package(Poco REQUIRED COMPONENTS ... NetSSL) requires an aditional find_package(OpenSSL) since poco-10.

poco (portable components) https://pocoproject.org/

Many of the necessary fixes do end up getting pushed upstream, though, thinking especially of stuff like converting CMake projects to use the GNUInstallDirs standard, so there is a benefit to the strictness work that extends beyond even just the Nix community itself.

Of course, sometimes those kinds of changes just never get merged, for a variety of well-understood open-sourcey reasons, eg: https://github.com/pocoproject/poco/pull/3105