Feature Request

Is your feature request related to a problem? Please describe:

This is a really minor nit, but the EXPLAIN output on binary strings is different from what I expected:

CREATE TABLE t1 (
 id INT NOT NULL PRIMARY KEY auto_increment,
 b varchar(255) not null,
 c varbinary(255) not null,
 index (b),
 index (c)
);


INSERT INTO t1 (b,c) VALUES ('a', 'a'),('b

Issue Description

What was unclear/insufficient/not covered in the documentation

How to update and increment in one single query

If possible: Provide some suggestion on how we can enhance the docs

Add this to the docs.

Additional context

#7268

Issue Template Checklist

In PostgreSQL, @ is a unary operator that returns the absolute value of a number. For example:

jordan=# select @ -5.0;
 ?column?
----------
      5.0
(1 row)

CockroachDB is missing such a unary operator.

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

We consider to introduce the SqlSessionManager on reference documentation. It provide thread safe implementation of SqlSession.

Related issues

• #1529

Environment

Knex version: 0.20.10
Database + version: Postgres 12

Bug

1. Explain what kind of behaviour you are getting and how you think it should do

knex.raw("?", [
  knex.insert({ id: "b", fields: { a: undefined } }).into("test"),
])

2. Error message

Feature request description

For now the only way to add TLS validation is though code with RegisterTLSConfig. With providing certificate path though DSN (like pq is doing it) all existing applications will receive TLS certificate validation out of the

We are suddenly running out of background workers and were told on Slack to increase timescaledb.max_background_workers from 8 to 16.

The documentation makes it seem like the timescaledb-tune tool will automatically set the key to a correct value. However the tool [always sets the value to 8](https://github.com/timescale/timesca

sql如下：select * from testreg where text.keyword <> REGEXP("?")
翻译的dsl如下：可以看到翻译的dsl是must，应该是must_not才对
{
"from": 0,
"size": 200,
"query": {
"bool": {
"filter": [
{
"bool": {
"must": [
{
"regexp": {
"text.keyword": {
"value": "?",
"flags_value": 65535,
"max_determinized_states": 10000,
"boost":

Describe the problem

We should test on larger datasets that are commonly used in