Charmander
Charmander
`ssl=false` isn’t supported by libpq, only `ssl=true`. Incompatibilities already exist between pg-connection-string and libpq, but I’m against adding new ones. (`sslmode=disable` is the correct version.)
Aren’t the BSD and ISC licenses equivalent in permissions? Not sure how that’s a critical update.
You should use `UNNEST` or `COPY` instead of building a dynamic query.
I’m pretty sure libpq and Node can’t use different OpenSSL versions. See #70 for the same issue in reverse.
@lukasa1993 yes (try it!)
@jorinvo You shouldn’t need the full `postgresql-dev`, just `libpq`.
Your Node and libpq need to be linked against [ABI-compatible OpenSSLs](https://www.openssl.org/policies/general/versioning-policy.html) (compare `openssl -version` to `node -p process.versions.openssl`, usually), i.e. both 1.1.\* or both 3.\*.\*.
Not sure why any part of this would be specific to the combination of pg and Cloud SQL, although it looks like Cloud SQL already has documentation at https://github.com/GoogleCloudPlatform/cloud-sql-nodejs-connector. Why...
The error message will be fixed by brianc/node-postgres#2372. I don’t think skipping loading the module tree entirely will happen in 8.x; it’s hard to make backwards-compatible, for not much benefit.
Weasyl/misaka@90aad1b and Weasyl/misaka@548d921 (minus the change to `find_emph_char` that Redcarpet seems to have applied already) might fix this.