Bobbie Soedirgo

This repo is decoupled from the UI - the UI can do ad-hoc queries and thus can support multi-columns constraints, but ideally this would be handled from a dedicated endpoint...

Prior arts: - [Prisma](https://www.prisma.io) - [Zapatos](https://jawj.github.io/zapatos/)

@thomas-coldwell this one's a bit different, the aim is to generate the types for your tables & columns, so you don't have to manually write something like this yourself: ```ts...

This issue has been stalled for a while - I suspect we'd need to sort out https://github.com/supabase/supabase-js/issues/170 first (updating type implementation especially) before we do this.

@mr-bjerre it's technically possible, but would need more work to make arguments type-safe from pg-meta itself. So yeah `.rpc()` isn't type-safe atm.

The jury's out if we can make it type-safe, but yes ideally we'd have type-safety. Re: `select`s there has been some progress here: https://github.com/supabase/postgrest-js/issues/217 (credits to @bnjmnt4n)

In hindsight, I wonder if this would require a lot of refactors in Studio. If there are a lot of call sites that rely on the old response format, we...

Thanks for looping in @eeeebbbbrrrr! > Forget things like pl/v8 and javascript -- write a Typescript-to-Rust transpiler. One problem I have with this is that TS and Rust are both...

Can you do it with `@supabase/supabase-js@rc`? We'll be releasing it as `@2` in a few weeks. `@supabase/supabase-js@1` likely won't be updated anymore.

See also https://github.com/supabase/postgrest-js/issues/273: > This is because numbers in JS are float64, so if your number is more than Number.MAX_SAFE_INTEGER === 9007199254740991 it won't be represented correctly. > An alternative...