Supabase JS sometimes type safe, sometimes not?

take this setup:

import type { Database} from './supabaseDef';
const supabase = createClient<Database>('https://secret.supabase.co', 'sb_publishable_secret')
const { data, error } = await supabase.from('myTable').select().order("id", { ascending: false })

import type { Database} from './supabaseDef';
const supabase = createClient<Database>('https://secret.supabase.co', 'sb_publishable_secret')
const { data, error } = await supabase.from('myTable').select().order("id", { ascending: false })

import type { Database} from './supabaseDef';
const supabase = createClient<Database>('https://secret.supabase.co', 'sb_publishable_secret')
const { data, error } = await supabase.from('myTable').select().order("id", { ascending: false })

import type { Database} from './supabaseDef';
const supabase = createClient<Database>('https://secret.supabase.co', 'sb_publishable_secret')
const { data, error } = await supabase.from('myTable').select().order("id", { ascending: false })

the

.from

.from

.from

.from is type safe, and I get error if I try to use a table not specified in the generated type file
but
the

.order

.order

.order

.order is not type safe and I can put anything there, if the column doesn't exists, it fails silently which is terrible

am I doing something wrong?

vick•9/11/25, 8:51 PM

I confirm this behavior regarding typescript. I didn't try running the code to see what happens at runtime. I would expect it to be strict here as well, but maybe it has something to do with order by on joins making it hard. I don't know. I'd file a bug report if it concerns you enough.

Supabase JS sometimes type safe, sometimes not?

Similar Threads

Similar Threads

Similar Threads