spago | SpaGo is toolkit for Single Page Application

In SQL SERVER 2017 + / Postgres:

The PureScript compiler creates mostly ES3 code. This is on purpose because Ecma Script is strictly backwards compatible and ES3 code runs in a ES5-, ES2015-, ES2016- (and so on) environment. This means that code created by the PureScript compiler runs even in older browsers.

If you are coming from TypeScript or Babel, you might be used to being able to choose the target. This is because these compilers work with plugins that run after each other. But the PureScript compiler does not have such a feature (since it is not transforming JS to JS like these specific compilers).

So what can be the benefit of targeting a newer version? Code size, performance and features. If you want to use new ES2015 features in your FFI code there is great news: You can make use of these features now in PureScript 0.13. There are also talks about making the compiler target newer JavaScript environments in the future for the benefits mentioned above. If someone would have to support older environments they could still add Babel to their toolchain. But PureScript is a small community project and neither performance nor code size are of a very high priority for the project (and if they were, there would probably be other optimisations that could yield much greater results).

As you can maybe infer from the README of purescript-assert, the Test.Assert module is only a super basic assertion library for authors of actual testing libraries (because they can't use their own library without causing circular dependencies).

It is therefore not supposed to give very good error stacks and location information. Packages that use assert often do a bunch of logging in between:

Found this fork that solves the problem:

https://github.com/j-nava/purescript-mongo

it was as easy as:

Firstly, that's not what spago install does. Instead of "adding a package to your project", spago install downloads all packages that are currently referenced in your spago.dhall file.

Secondly, the idea with Spago is that you don't choose a specific package version. Instead what you choose is a "snapshot", which is a collection of certain versions of all available packages that are guaranteed to compile and work together. This is a measure intended to prevent version conflicts and versioning hell (and this is similar to how Haskell stack works)

The snapshot is defined in your packages.dhall file, and then you specify the specific packages that you want to use in spago.dhall. The version for each package comes from the snapshot.

But if you really need to install a very specific version of a package, and you really know what you're doing, then you can modify the snapshot itself, which is described in packages.dhall.

By default your packages.dhall file might look something like this:

This happens because type inference doesn't work very well with constraints. It doesn't always know if it needs to move constraints to the top or leave them in place. In general this is an undecidable problem, the compiler just tries to make the best effort.

Try this in the REPL:

I see the below in your error logs

org.postgresql.util.PSQLException: ERROR: relation "fattura_intestazione" does not exist.

Seems it's looking for fattura_intestazione at some point of your report execution mostly during parameter page execution.

I feel you need to handle some unexpected condition of your parameter. I would suggest take fattura_intestazione as a pointer and proceed further.

It was memory issue.. Connection to Foodmart database was not getting opened.. We upgraded our server to server with bigger memory.. and this issue got resolved..