There is a lack of global link styles, which is an accessibility issue.

(Old part of the issue)

Steps to reproduce:

1. Try to tab throu

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

Intended that the full output is bolded?

Environment

Knex version: ^0.21.17
Database + version: postgres 13
OS: MAC OS Catalina 10.15.7
Additional Info: Running this with docker-compose using the latest postgres image (v13), node 14-alpine

Bug

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

I'm not sure if this is a bug with knex, or just a [documentation bug](https://knexjs.org/#Schema

Hi,
I found a documentation error.
Address url: https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/usage/startup/
ext-lib are right, lib-ext are not right. it ’s need correction.

Overview of the Issue

vtexplain panics on SHOW TABLES and SHOW FULL TABLES

Reproduction Steps

Steps to reproduce this issue, example:

1. Deploy the following vschema.json:

{
    "ks1": {
        "sharded": true,
        "tables": {
            "user": {
                "column_vindexes": [
                    {
                        "column":

Describe the Bug

Hi. I've added a repeater interface for my JSON object, and set the fields as follows:
itemid: integer
quantity: integer

When requested from the API, the numbers are returned as strings. Example response:
[{"itemid":"3","quantity":"5","stackable":true}]

Note that the boolean type works correctly as opposed to integers.

To Reproduce

• Create a collection with

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