What happened:

When I click the link for See supported log levels and mappings of log level abbreviation and expressions in the Logs Panel doc it gives me a 404.

What you expected to happen:

It should take me to the See supported log levels and mappings of log level abbreviation and expressions page if it still exists.

**How to reproduce it (as minimally and precisely a

Issue Description

While using model.bulkCreate, as we pass the options, an object which contains transaction, it comes modified after the execution

What are you doing?

We have called bulk

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

Environment

Knex version: 0.21.1
OS: docker node:latest

I'd like to be able to write my migrations (and seed) files as es modules with the .mjs file extension like I'm doing with all my other javascript files.

I'd like to be able to run these migrations from within node (not via the cli) like this:

db/migrations/00001-users-table.mjs:
    export const up = knex => knex.sche

Problem Statement

There are users who would like to secure the http port exported by the vitess servers with TLS. However, some of the health check and monitoring URLs (like /debug/vars) still need to be accessed without TLS. For example, Kubernetes prefers the health check URLs to not require TLS.

We require the ability to specify a separate (optional) TLS http port, and the ability to s

Issue description

Go 1.15 will introduce a new Validator interface, which may be implemented by Conn to allow drivers to signal if a connection is valid or if it should be discarded:

https://tip.golang.org/pkg/database/sql/driver/#Validator

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

It is idiomatic for JWTs to be accepted using a header format of Authorization: Bearer <JWT> (see jwt.io introduction.) In general, in history, the RFCs surrounding the authorization header have taken care to specify the mode of Authorization as the first part of the header value (e.g. Basic, Di

Makes it just that little nicer to use

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

Problem

There are some servers like fastify that allow to define json schemas in order to provide better performance and input / output data validation. Right now I am using prisma with fastify and have to manually define such schemas. Most of these, however, would