nquery | Generic SQL engine for Web and Big-data | SQL Database library

I ve no idea why it looks is getting bool(__x) <=> false as an bool and int comparison. I would think you got some strange macro in your files included before to include the header that is going to break the standard code. I would suggest you try to move above the standard headers and below them your 'user defined' headers.

One of the issues I see here is that your controller is doing all the work - getting a query, setting it up, executing it, and returning the results from the API call. Doing all these things in one place makes it hard to test. That also raises a question - what exactly are you trying to test? And what issues are you running into?

You might want to look at refactoring it to use a layered architecture instead. API -> Service Layer -> Repository layer.

This might be a cleaner structure, and you can then test layers independently:

1. Check that the API calls the correct service layer method with the correct parameters.
2. Check that the service layer calls the repository with the correct arguments.
3. Check that the repository creates the correct query.

Alternatively, you could also do integration testing - just invoke the API and make sure that the correct result is returned.

Also, be wary of using String replacement in your queries. Rather have a look at PreparedStatement (https://docs.oracle.com/javase/tutorial/jdbc/basics/prepared.html).

The square brackets "[]" shall not be in quotes since now they are interpreted as string ... , they need to be added just as square brackets [] and require in golang: &[]int{} to be translated by the mongo goland driver to empty array ...

You just need to check for null before attempting to call toString():

This is an issue with Arcadia and the version of KSQL that you're running.

There was a breaking change in ksqlDB 0.6 (shipped with Confluent Platform 5.4) which changed the syntax of queries. Pull queries were added and the previous "continuous queries" are known as "push queries" and denoted with a mandatory EMIT CHANGES clause.

shinyjs can enable/disable buttons for us. grepl can tell us if a string contains another string. The below minimal example shows this in action:

node:12444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). Above error, clearly says that you should handle promise rejection as you are throwing error

When status code is 400 or more than this code is

If You want to return result of query so simply do following things:

1) add query method to db module:

You are correct about the flow and that the SAML 2.0 Authn Response are generated right away. You need to implement the login dialog and username/password validation your self as you can see in my comment // **** Handle user login e.g. in GUI ****.

Meaning that you need to cut the Login method in half. After the first half of the Login method you need to start some kind of sequence insight the IdP where the user is authenticated. And then return to the second half of the Login method which issues the SAML 2.0 Authn Response.