@jxpatto/pgquery
v0.0.1
Published
Query postgres from node red. Uses mustache templating to build query strings
Downloads
3
Readme
node-red-contrib-pgquery
Disclaimer
THIS IS A FORK AND WIP rewrite - forked from here. Currently, a work in progress, will cut a 1.0.0 release and npm package when it is ready.
The current upstream repo seems to be abandoned, and I am using this for my own setup. I will be making changes and updates and documenting them here. I will also be publishing this as a npm package if others would like to use it. Feel free to submit pull request.
~Jess Patton
Current Changes - on branch rework
- Updated packages pg and mustache to the latest versions, removed co.
- Now uses async/await instead of co.
- Rewrote query node to use simplified async flow.
- Rewrote configuration node to use new pg 8 syntax.
Issues I ran into, and ways to fix them.
These are issues I ran into and could not find documentation about. I will also be trying to update to code to handle some of these situations better in the future, but for now, here are some work arounds.
INSERTS:
Take this insert for example.
INSERT INTO public.baby_events ("createdAt", event_id, description) VALUES (now() at time zone 'utc', {{msg.payload.event_id}}, '{{msg.payload.description}}')
When doing an insert, or even a select using postgrestor, there are some columns and values that need massaging to get to work as expected.
- When the value that is inserted is a string, or type text, you have to surround it with
'
, otherwise it will be passed in with"
and be treated as a column name, rather than a value. You can see me do this here with'{{{msg.payload.description}}'
. - If you get an error that a column name does not exist, try surrounding it with
"
. You can see I had to do that with"createdAt"
. Without those I received an error that says something likecreatedat column did not exist
.
Description
pgQuery :space_invader: is a Node-RED node allowing basic access to Postgres :elephant: database.
Postgrestor sets up a console to execute queries against the configured database.
msg.payload
will contain the result object of the query. It has the following properties:
command
: The sql command that was executed (e.g. "SELECT", "UPDATE", etc.)rowCount
: The number of rows affected by the SQL statementoid
: The oid returnedrows
: An array of rows
Postgres implements a template engine allowing parameterized queries:
/* INTEGER id COLUMN */
SELECT * FROM table WHERE id = {{ msg.id }}
/* VARCHAR id COLUMN */
SELECT * FROM table WHERE id = '{{ msg.id }}'
Installation
STILL WIP, UPDATED INSTALL COMING
Using the Node-RED Editor
From version 0.15 of Node-RED you can install Postgrestor directly using the editor. To do this select Manage Palette
from the menu (top right), and then select the install
tab in the palette.
You can now search for pgquery to install.
Installing npm packaged nodes
To install pgquery npm-packaged node, you can also, either install it locally within your user data directory (by default, $HOME/.node-red
):
cd $HOME/.node-red
npm i @jxpatto/pgquery
or globally alongside Node-RED:
npm i -g @jxpatto/pgquery
You will need to restart Node-RED for it to pick-up pgquery.