Database

Hi, I'm trying to read a CSV file like this (;, delimiters):

A;B;C;D
1,1;2,2;3,3;4,1
1,1;2,2;3,3;4,1
1,1;2,2;3,3;4,1

What happens: semicolon from the first line does not become the main separator, the comma from the second line does and it breaks the file's logic.

Code that reads:

X.read(e.target.result, { type: 'string' })

Result

{
      A1: { t: 's', v:

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

Currently, tree.NotExpr is implemented natively in the vectorized engine, so we have to fallback to the older row-by-row engine to evaluate it. We should, instead, vectorize NotExpr.

I think the implementation will be quite similar to how tree.IsNullExpr implemented, and I think we will want to implement two version of NotExpr operator:

• one for projections, which populates a `coldata

MeiliSearch v0.23.0

When sending documents or creating an index, the Content-type requirements are not the same

• Creating an index

curl -i \
  -H 'Content-type: application/json; charset=utf-8' \
  -X POST 'http://localhost:7700/indexes' \
  --data-binary '{"uid": "test"}'

-> The index is created

• Sending documents

curl -i \
  -H 'Content-type: applicatio

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

在10.cluster章节中，第一段提到了“要了解TDengine 2.0的集群管理，需要对集群的基本概念有所了解，请看《TDengine整体架构》一章。”
为了便于用户理解，应该如后面所述的“《立即开始》”一样，为《TDengine整体架构》加上跳转链接。

《TDengine整体架构》这一章的链接如下：https://www.taosdata.com/cn/documentation/architecture

文档仓库如下：[10.cluster](https://github.com/taosdata/TDengine/blob/develop/documentation20/cn/10.cl

Currently, all Directus system collections have a description except directus_panels and directus_dashboards... let's add those:

Dashboards — Dashboards within the Insights module
Panels — Individual panels within Insights dashboards