senthadev

pipeSQL author here:

Sorry, I didn't understand your answer. It is very important to understand the complex query in-order to debug or re-engineer. One way is to visualise it as mentioned in the article and convert it to SQL via pipeSQL.

Piping is used to merge the tables rows. Tables can be merged in multiple ways, for example by join, left join, exists, not exists, union, minus etc.. And you can have the pipe chain up to 255 levels.

This is an example where SQL can be written in multiple ways to get the same result. It doesn't matter how many lines SQL contains since its all depends on how the database engine going to execute it. Therefore, pipeSQL's main aim is to make it easier to read and understand the query after couple of days/weeks :) .

This is not a replacement for SQL. Its a tool to create SQL in a different angle. An angle which is similar to UNIX pipeline concept.

API would be charge by usage. But the desktop APP will be one time payment(per year) since it will include the parser to translate the pipeSQL to database dialect. Still not finalised, but happy to hear your thoughts on the pricing model.

Main aim of this tool is to create complex queries in a bottom-up approach. Say you want to create a query by joining 5 tables. Even though we declare 5 tables in the FROM clause, database will join 2 at a time. And then join another table with the previous result set. So this tool helps to build query similar to execution plan tree structure.

This is a tool to generate complex queries in a bottom-up approach. Once the SQL is generated, then we can use the SQL in the application for future use. It's not another layer between apps and database.

Exactly, its a tool to generate SQL in a elegant manner. Once the SQL is generated, we can uses the generated SQL in the app. There is no need of a new additional layer between apps and database.

How about sending binary SMS such as SIM-RFM messages?