Improve documentation

Link

https://github.com/supabase/supabase/blob/master/DEVELOPERS.md

Describe the problem

The docs on getting started with contributing to supabase are very basic and need some work.

Describe the improvement

Add links to docs, improve getting started docs, add links to where people can ask for help, etc.

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.

Please complete method YamlProxyConfigurationSwapperTest.assertReadwriteSplittingRuleConfiguration()

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

<img src=

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.

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

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

Consider the following code (using AsChangeset instead / in addition to Insertable produces the same error message):

#[derive(Insertable)]
struct Foo {
        #[column_name = "type"]
        ty: String
}

This code is wrong because eventhough the table has a column called type, the auto-generated schema.rs file renames that to type_ to avoid using a keyword as an

Describe the bug

No response

To reproduce

create table pricetable2
(ts timestamp,symbolname SYMBOL CACHE ,price Double,aggregateTradeId Long,firstTradeId Long,lastTradeId Long,buyerMaker Boolean,qty Double) 
partition by day;

Executes without error and crates table without designated timestamp partitioned by DAY

Expected Behavior

Create table query sh