Charmander
Charmander
Note that “prepared statements” in the sense of the extended query protocol also includes any query with a parameter. Like the other times this error has come up in issues:...
@ljharb Wouldn’t that be `const slice = [].slice; arraylike::slice()`? Or, to use method extraction, `const slice = ::Array.prototype.slice.call; slice(arraylike)`.
@gazebosx3 That’s not possible in general. `fileSizeLimit` is checked as the stream for the file is read, i.e. *after* the `file` event is emitted.
How about a non-parameterized query, i.e. a hardcoded literal instead of `$1`?
see also #189
@adaboese You can pass your SSL configuration in the `ssl` property of the pg configuration object instead of implicitly through environment variables (and that `ssl` property can still be constructed...
This library doesn’t support `PGHOSTADDR`, and the JS driver doesn’t support `PGSSLCERT`/`PGSSLKEY`/`PGSSLROOTCERT` environment variables. You need to pass them manually in the `ssl` property of [the configuration object](https://node-postgres.com/apis/client#new-client) for now.
What will you use pg-connection-string for on the browser?
This is caused by f305419676afe79a91dc7863289f7f97ac6db3d5 from #2971. > The above resulting code returns the connectionString object to be, if passed a database name of "fooBar", to just be "fooBar" if...
> `sslrootcert=system` might already be the default behavior of node-postgres (it is)