Database

What happened?

In a Jepsen test run of five etcd 3.5.3 nodes, with process pauses (sending processes SIGSTOP and SIGCONT), compaction (performed via the admin API), and defragmentation (via etcdctl), one etcd process crashed with the following error message:

{"level":"panic","ts":"2022-06-13T14:11:27.870Z","caller":"etcdserver/apply.go:638","msg":"unexpected error during txn","error

Enhancement

Some system variables either have no type (default: TypeString) or use TypeString when they could use a different builtin type (TypeInt, TypeEnum, TypeBool) that is more suited. Here is what I found from manual inspection:

While writing string data (example = "121212121212121" -> string of all integer characters) into excel.
while user download and see, the downloaded xl/CSV, the data is shown in exponential format. Is there a way to show the same data. without converting into exponential in this case.

Currently, when pushing a tag to this git repository, this CI is triggered, publishing a docker image with the name of the tag (and latest if it's a GitHub release).
It means if the v0.27.0 tag is pushed, the v0.27.0 docker image will be available.

We would like to update [this CI](https:/

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

There are several optimization the execution engine can perform when evaluating LIKE patterns with %, which matches zero or any number of any character. For example, see #80073.

Sequential %s can prevent these optimizations, but they are semantically equivalent to a single %, so the optimizer should normalize them to a single %.

For example:

-- The following expressions 

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

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

To Reproduce
Steps to reproduce the behavior:
N/A

Expected Behavior
fix following issues found by Coverity Scan in taosdump.c

1. String not null terminated High TDengine/src/kit/taos-tools/src/benchUtil.c postProceSql
2. Resource leak High TDengine/src/kit/taos-tools/src/taosdump.c parse_json_to_recordschema
   3

Describe the Bug

To Reproduce

Make sure you have a lot of rows in a table and then change the table spacing to compact.

Errors Shown

None

What version of Directus are you using?

9.8.0

What version of Node.js ar

Hi community,

This issue is for WeOpen-Star

We need to add more unit test for DatabaseTypeEngine.

• DatabaseTypeEngine#getProtocolType
• DatabaseTypeEngine#getStorageType
• DatabaseTypeEngine#getDefaultSchemaName