SQL

lightning v5.3.0

After the content in parquet may be written by spark, the definition of bool is true or false. Regenerating the parquet file takes time, In tidb, bool behaves as tinyint, so proper type conversion will help improve the success rate of lightning import

parquet file：
![image](https://user-images.githubusercontent.com/21033020/147809823-214dcb34-0e10-4566-aa75-2109c0525144

Issue Creation Checklist

• I have read the contribution guidelines

Feature Description

When SQL errors occur, make the 'mes

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

The array overlap operator, &&, provides a convenient syntax for filtering for arrays that have one more more elements in common with another array. However, the && operator is not index accelerated, so an efficient inverted index scan in not planned. The current workaround is to rewrite the query by combining the containment operator with OR expressions:

CREATE TABLE movies (
  

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.

In https://github.com/taosdata/TDengine/blob/develop/src/client/src/tscPrepare.c, Local variable loopCont is assigned only once, to a constant value, making it effectively constant throughout its scope. If this is not the intent, examine the logic to see if there is a missing assignment that would make loopCont not remain constant.

So the 1567th line should be removed.
![image](https://user-im

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

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

Can't use 'Comment' as column alias.
To reproduce:

$ dolt version
dolt version 0.37.0
$ dolt init
$ dolt sql
Dolt>  SELECT TABLE_COMMENT AS Comment FROM information_schema.TABLES;
Error parsing SQL
syntax error at position 32 near 'Comment'
SELECT TABLE_COMMENT AS Comment FROM information_schema.TABLES
                                ^
Dolt> 

Hi,

my admin portal looks like this :

Version

• Server Installed 1.38.4
• Server Latest 1.38.4
• Web Installed -
• Web Latest 2.17.1

It seems that, at some point, 'GetInstalledWebVersion()' in 'Admin.dll' is called? Could anyone help me understand what do I need to check, to fix this?

Hi all. Congrats for the amazing software :)

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

It would be amazing to have the IN operator available in this drop-down list:

Describe the solution you'd like

Have the IN oper

Describe the bug

ATM the following query

select * from t where abyte = null;

executes just fine and returns rows with abyte column equal to zero. The same happens for short columns.

Byte and short column types don't support nulls (important note: geobyte and geoshort types support nulls), so we need to do something with this behavior. We could either report an error for

• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect