Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 17 of 23

supabase

query loading

supported — Laygent v1 implements query loading in its supabase target.

Requirements and limitations
Id
supabase.query_loading
Status
supported
Aliases
  • query loading
  • supabase query loading
  • use query loading
  • add query loading
  • support query loading
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

query ordering

supported — Laygent v1 implements query ordering in its supabase target.

Requirements and limitations
Id
supabase.query_ordering
Status
supported
Aliases
  • query ordering
  • supabase query ordering
  • use query ordering
  • add query ordering
  • support query ordering
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

queues

unsupported — Laygent v1 does not implement queues in its supabase target.

Requirements and limitations
Id
supabase.queues
Status
unsupported
Aliases
  • queues
  • supabase queues
  • use queues
  • add queues
  • support queues
Evidence
Limitation
Laygent v1 does not implement queues in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

realtime broadcast

unsupported — Laygent v1 does not implement realtime broadcast in its supabase target.

Requirements and limitations
Id
supabase.realtime_broadcast
Status
unsupported
Aliases
  • realtime broadcast
  • supabase realtime broadcast
  • use realtime broadcast
  • add realtime broadcast
  • support realtime broadcast
Evidence
Limitation
Laygent v1 does not implement realtime broadcast in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

realtime postgres

unsupported — Laygent v1 does not implement realtime postgres in its supabase target.

Requirements and limitations
Id
supabase.realtime_postgres
Status
unsupported
Aliases
  • live database updates
  • realtime subscription
  • postgres changes
  • live records
  • realtime postgres
  • supabase realtime postgres
  • use realtime postgres
  • add realtime postgres
  • support realtime postgres
Evidence
Limitation
Laygent v1 does not implement realtime postgres in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
  • refresh-driven data loading
supabase

realtime presence

unsupported — Laygent v1 does not implement realtime presence in its supabase target.

Requirements and limitations
Id
supabase.realtime_presence
Status
unsupported
Aliases
  • realtime presence
  • supabase realtime presence
  • use realtime presence
  • add realtime presence
  • support realtime presence
Evidence
Limitation
Laygent v1 does not implement realtime presence in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

relationships

supported — Laygent v1 implements relationships in its supabase target.

Requirements and limitations
Id
supabase.relationships
Status
supported
Aliases
  • relationships
  • supabase relationships
  • use relationships
  • add relationships
  • support relationships
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

resumable uploads

unsupported — Laygent v1 does not implement resumable uploads in its supabase target.

Requirements and limitations
Id
supabase.resumable_uploads
Status
unsupported
Aliases
  • resumable uploads
  • supabase resumable uploads
  • use resumable uploads
  • add resumable uploads
  • support resumable uploads
Evidence
Limitation
Laygent v1 does not implement resumable uploads in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

rls

supported — Laygent v1 implements rls in its supabase target.

Requirements and limitations
Id
supabase.rls
Status
supported
Aliases
  • row level security
  • RLS
  • database policy
  • access policy
  • rls
  • supabase rls
  • use rls
  • add rls
  • support rls
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

rpc

unsupported — Laygent v1 does not implement rpc in its supabase target.

Requirements and limitations
Id
supabase.rpc
Status
unsupported
Aliases
  • rpc
  • supabase rpc
  • use rpc
  • add rpc
  • support rpc
Evidence
Limitation
Laygent v1 does not implement rpc in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

secret configuration

supported — Laygent v1 implements secret configuration in its supabase target.

Requirements and limitations
Id
supabase.secret_configuration
Status
supported
Aliases
  • secret configuration
  • supabase secret configuration
  • use secret configuration
  • add secret configuration
  • support secret configuration
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

select queries

supported — Laygent v1 implements select queries in its supabase target.

Requirements and limitations
Id
supabase.select_queries
Status
supported
Aliases
  • select queries
  • supabase select queries
  • use select queries
  • add select queries
  • support select queries
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None