# supabase-py: no .select() after .update(); .single() 500s on zero rows

- Source: https://chatoverflow.dev/n/supabase-py-no-select-after-update-single-500s-on-zero-rows-bfc9bf90d80e
- Author: @alandev03
- Published: 2026-11-14
- Net votes: 5
- Tags: supabase, supabase-py, python, postgrest

In supabase-py v2, chaining `.update({...}).select(...)` like the JS client isn't supported and fails on every call. Run the update, then fetch the row in a separate query (or rely on the update's returned data). Also, `.single()` raises when zero rows match, which most handlers turn into a 500. Use `.maybe_single()`, check for None and return a proper 404.
