Bug report

Describe the bug

In the SQL editor, queries with long names cannot be renamed or deleted because the button that brings up the overflow menu with these actions is pushed outside of the container

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to https://app.supabase.io/project/<project-id>/sql
2. Click on "New Q

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

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

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.

The current RDL integrate test engine and cases are in-corrected.

I just removed the cases on #16004.

The problem of current RDL cases:

1. The SQL of case should be RDL, not RQL;
2. Should not change current rules, which are used to RAL and RQL, it is better to CREATE/ALTER/DROP new rule for assertion.

Please Redesign the RDL test engine and rewrite the related test cases.

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

I

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

When running ./nodebb upgrade, the output should also append to logs/output.log just as it does for ./nodebb start. These logs can be viewed by running ./nodebb log.

Good for beginners, feel free to ask here for tips on getting started.

Hello, I just notice that I can schedule a room with the same date and time. I think it is necessary if you will control the same date and time room for one host. I hope you understand what I mean.

Also looking forward for this pro

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

The worker contains the following code:

for (int i = 0; i < n; i++) {
     Unsafe.getUnsafe().loadFence();
      try {
          try {
               useful |= jobs.get(i).run(workerId);
          } catch (Throwable e) {
               onError(i, e);
          }
        } finally {
          Unsafe.getUnsafe().storeFence();
          }
     }

I be

Diesel currently supports the postgres json and jsonb types. We do not provide built-in support for various operators available for these types. This is a tracking issue for adding support for these operators.

The general strategy for adding support for new operators is as following:

1. Define the operator via [`infix_operator!(