[vkb]

This might be good for developers, but I'm not sure how it's helpful for either heavy users or beginners. For business analysts, it's just another layer on top of SQL, which slows down processing time, and for beginners, it's now two types of syntax and order they have to learn instead of one.

[rnovak]

I don't even think it should be used with Devs. For one, a good dev should know how to build queries, otherwise he/she is missing a good foundation, in which case shouldn't be working with the db. Just my personal take though

[icebraining]

I know how to write assembly, but I still develop most of my software in Python. If this makes hairy queries more readable, I can see the use case, even if it doesn't replace SQL itself or the need to know it.

[slimbods]

I don't think it is another layer, and I don't think it ties you to a vendor. This is a query builder tool that produces SQL code. You then take that SQL and run it against the DB. Once you've generated the SQL, you can modify it, you're not tied to the original pipesql.

[senthadev]

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.

[adamtj]

That doesn't make any sense. What happens when you need to change the SQL?

To an application developer, this looks like nothing more than a code generator. Generated code is not source code and it should not be edited directly. Rather, you should change the generated code's source code and then re-generate it. While it may not be a layer between the app and the database, it's definitely an extra step in your build chain.

You'd be foolish to tie your application's build process to a cloud service that may disappear without warning. No sane developer would do such a thing. I don't see how this is any use to developers in any form other than a standalone compiler.

[senthadev]

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.