SQL

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

mysql> create table t ( b timestamp(3) NOT NULL DEFAULT '1970-01-01 08:00:01.000' COMMENT '');
Query OK, 0 rows affected (0.08 sec)

mysql> show create table t;
+-------+--------------------------------------------------------------------------------

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

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

https://github.com/sequelize/sequelize/blob/8a1429d6044123bba3a3f312b2e0c74b0c829990/lib/model.js#L1271

If I create any model with
charset: 'utf8mb4', collate: 'utf8mb4_general_ci'

sequelize translates it to this for mysql

CREATE TABLE IF NOT EXISTS tablename ... ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8mb4_general_ci;

On stepping through the code, it seems that the issu

When a roachprod user runs grafana-start, regardless of whether they pass a grafana-config, a user should be able to see a default dashboard, perhaps with the following pages.

Jira issue: CRDB-17197

Bug Description
fix issues found by Coverity Scan in syncMain.c

To Reproduce
N/A

Expected Behavior
fix following issues:
| issue type | category | file path | function | line number |
| -------------------------- | -------------------------- | -------------------------- | -------------------------- |

Describe the Bug

The Markdown field interface it's editable when readonly
(you can see that it's readonly in the raw value)

https://user-images.githubusercontent.com/1007051/177955838-d978c4ea-2f61-4a58-b7aa-4eb43cc7336b.mov

It works well with the Textarea interface:
<img width="833" alt="Screen Shot 2022-07-08 at 10 52 21" src="https://user-images.githubusercontent.com/1007051/177955

Feature Request

For English only, other languages will not accept.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Is your feature request related to a problem?

Yes, refer t

Currently we only support Upsert for CockroachDB. Implementing same for MySQL should be pretty straightforward as well.

Wonder if we can also use INSERT ON CONFLICT UPDATE for PostgreSQL to ensure operation with same signature also works.

Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:

• All unquoted column names are treated as upper case
• Quoted column names are case sensitive.

So "date_from" <> date_from

To Reproduce
Steps to reproduce

Using dolt sql -q "<query>" -r csv > file.csv results in newlines in the output data:

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

Is your feature request related to a problem? Please describe.
with the implementation of copy to clipboard it would be very useful to have the option to copy with this pattern below (which I don't remember the name at this time)

Is your feature request related to a problem?

We have users periodically asking for week-based partitioning.

Describe the solution you'd like.

Add WEEK to the PARTITION BY options.

Describe alternatives you've considered.

No response

Additional context.

This PR should give enough hints on how to implement this feature: questdb/questdb#1571

As a result of the showcase, we should improve the following messages:

• “column does not exist”: Which one?
• “syntax error: unexpected IDENTIFIER”: Would like to
• have a hint where to look for the error in my statement.
• "pq: syntax error: unexpected $unk"