PG.js | package.js Generator | Generator Utils library

A new version of pg, namely 7.0.0, was published about 15 hours ago (from the time I'm writing this).

This version has lots of changes, one of them being that pg.connect has been hard-deprecated (in other words: removed) in favor of pg.Pool(...).connect(...), as documented here: https://node-postgres.com/guides/upgrading

The new method of connecting looks like this:

The way you've written your nodes in the contain an unnecessary : in the value= param. This is causing p to compute as NaN. Instead, rewrite as: 1000 2000 ...

Before cleaning up your repository, you should conduct two important preparations:

• Make sure your .gitignore file is up-to-date and contains all the correct patterns you want to ignore.

• Commit or stash any outstanding local changes you might have. Your working copy should be clean before you continue.

You cannot create prepared statements and cannot inject dynamic table or column names in the query because this would disallow preparing the statement completely. If you definitely have to do prepared statements, you need to know that in PreparedStatements the input datatypes (the dynamic variables) AND the return datatypes (the returned columns) MUST be defined. Since * will return differnet return types for different tables the above will never work. If you know for example that you always return an id and a name you might create a function in postgresql like this:

Don't use "display: none;" when transitioning an element in or out. All you're doing is showing / hiding something rather than having a smooth transition between styles.

If you want to animate things, do so buy adding a CSS class onto the elements you want to transition rather than changing the styles of those elements in JS.

For example, to slide something in from the left:

You are missing all the 'AppLauncher' code needed to launch dwv and load the image. The launcher code is the code you have put in the window.onload function of your first html.

Looking at the source of sankey.js, it's expecting them to be an index or the node object itself. You'd have to pre-process the data to do what you want. That's pretty trivial: