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

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().
})

• Add test case for SQLParserEngine
• Add test case for DatabaseTypedSQLParserFacadeRegistry with DatabaseTypedSQLParserFacade fixture
• Add test case for ParseASTNode

I am intentionally making this issue specific but I assume it could be expanded to include much more of the API.

Problem

I do not have the entire Prisma Client API perfectly (let alone roughly) committed to memory.

When I go to use it to query for many results the operations tell me nothing about what and why they will do. I only have types to work with.

I don't want to open my br

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.

Found an issue with a fresh install of Directus on a database with existing foreign keys/ relationships setup. The Many to One interface doesn't display when you enable it for existing foreign keys. Might be caused by the foreign key field not existing in the directus_relations table, as this table remains empty when enabling the interface.

Exact steps to reproduce this issue
- Create

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