You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you know what you're doing, you can use `unsafe` to pass any string you'd like to postgres.
366
+
367
+
```js
368
+
369
+
sql
370
+
371
+
```
372
+
373
+
358
374
## Errors
359
375
360
376
Errors are all thrown to related queries and never globally. Errors comming from Postgres itself are always in the [native Postgres format](https://www.postgresql.org/docs/current/errcodes-appendix.html), and the same goes for any [Node.js errors](https://nodejs.org/api/errors.html#errors_common_system_errors) eg. coming from the underlying connection.
@@ -366,6 +382,11 @@ There are also the following errors specifically for this library.
366
382
367
383
Whenever a message is received from Postgres which is not supported by this library. Feel free to file an issue if you think something is missing.
368
384
385
+
##### MAX_PARAMETERS_EXCEEDED
386
+
> Max number of parameters (65534) exceeded
387
+
388
+
The postgres protocol doesn't allow more than 65534 (16bit) parameters. If you run into this issue there are various workarounds such as using `sql([...])` to escape values instead of passing them as parameters.
0 commit comments