Issue Description

What are you doing?

I am trying to strongly type my application using Typescript and Sequelize. I have noticed th

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

λ npx prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma

✔ Generated Prisma Client (2.25.0) to .\prisma\foo in 738ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
```
import { PrismaClient } from './prisma\foo'
const prisma = new PrismaClient()
```

Note the ./prisma\foo. The path

Feature request

Is there any chance to have a Knex native way to set "DEFERRABLE INITIALLY DEFERRED" on a table with foreign key constraints ?

knex.schema.table('users', function (table) {
  table.integer('user_id').unsigned()
  table.foreign('user_id').references('Items.user_id_in_items').deferred().
})

Hi community,

This issue is for #10887.

Aim

Add unit test for shardingsphere-sql-parser-engine project to test its public functions.

Basic Qualifications

• Java
• Maven
• Junit.Test

Classes

Add unit test for classes to test its public functions.

• SQLParserEngine
• SQLVisitorEngine
• SQLParserFactory

Examples FYI

• SQLParserEngineTest

Since we've upgraded our ProtoBuf package version in vitessio/vitess#8075, the new serializer to JSON and ProtoText inserts random whitespace on its output that prevents byte-wise comparison.

Our test suite makes extensive use of "golden tests" that compare these outputs. In order to complete the upgrade successfully, I had to disable the randomness in the serializer.

Describe the Bug

The custom hooks are not being triggered for the read action.

![image](https://user-images.githubusercontent.com/14786440/124280461-fd603100-db48-11e

Issue description

This option will improve performance in many scenarios
https://dev.mysql.com/worklog/task/?id=8134

https://www.facebook.com/weixiang.zhai/posts/678596755543802

Describe the bug
If I pass 'Next 7 days' into the dateRange in query, the response is not a range over the next 7 days but only the day IN 7 days.

To Reproduce
Steps to reproduce the behavior:

1. Build a query like this:

const query: Query = {
    measures: [
      measure
    ],
    timeDimensions: [
      {
        dimension: 'Your.Dimension,
        dateRange: 'Next 7

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