npm install vertica
connect method with a connection options object. The following connection
options are supported.
host: the host to connect to (default:
port: the remote port to connect to (default:
user: the username to use for authentication
password: the password to use for authentication
database: the database to connect to. If your Vertica server only has a single database, you can leave this blank.
ssl: whether to encrypt the connection using SSL. The following values are supported:
false: no SSL
"optional": use SSL if the server supports it, but fall back to no SSL if not (default).
"required": use SSL, throw an error if the server doesn't support it.
"verified": use SSL, throw an error if the server doesn't support it or its SSL certificate could not be verified.
role: Runs a
SET ROLEquery to activate a role for the user immediately after connecting.
searchPath: Runs a
SET SEARCH_PATH TOquery to set the search path after connecting.
timezone: Runs a
SET TIMEZONE TOquery to set the connection's time zone after connecting.
initializer: a callback function that gets called after connection but before any query gets executed.
decoders: an object containing custom buffer decoders for query result field deserialization, see usage in custom decoders test.
Vertica = require 'vertica'connection = Verticaconnect host: 'localhost'user: "me"password: 'secret'throw err if err
connect will establish a single connection. A connection can only execute
one query at the time. Due to the evented nature of node.js, it is possible to start a new
query while another query is still running. This library implements a simple queueing
system that will run queries serially.
If you want parallelism, you will need multiple connections to your server. You can set up
connection pooling fairly easily using the
generic-pool library. Note that transactions
cannot be shared between multiple connections; you need to use the same connection for all
queries in the transaction and run them in serial.
pool = genericPoolPool:verticaconnectcallback errconn
Running a buffered query will assemble the result in memory and call the callback function when it is completed.
connection = Verticaconnect...connectionquery "SELECT * FROM table"consolelog errresultsetfieldsresultsetrowsresultsetstatus# or, identically:query = Verticaconnect...query "SELECT * FROM table"= ...
Running an unbuffered query will immediately emit incoming data as events and will not store the result in memory. Recommended for handling huge resultsets.
connection = Verticaconnect...query = connectionquery "SELECT * FROM table"# 'fields' is emitted once.queryon 'fields' consolelog"Fields:"fields# 'row' is emitted 0..* times, once for every row in the resultset.queryon 'row' consolelogrow# 'end' is emitted once.queryon 'end' consolelog"Finished!"status# If 'error' is emitted, no more events will follow.# If no event handler is implemented, an exceptions gets thrown instead.queryon 'error' consolelog"Uh oh!"err