Data model and database
Supabase PostgreSQL holds Toolora’s application records alongside Auth and Storage metadata. Active migrations define schema changes, constraints, policies and functions. Browser queries use database policy; privileged services must supply their own authorization checks. Detailed schema reference requires domain-specific diagrams and function inventories beyond these summaries.
Records, relationships and projections
Section titled “Records, relationships and projections”The records, relationships and projections concept traces identity, accepted work and invoice evidence to their owning records. It distinguishes global and company identity, source links, copied snapshots, consumption and external observations. The domain model supplies their business meaning. A projection’s presence does not establish source completeness, agreement evidence or permission to change the originating record.
Row-level security
Section titled “Row-level security”The row-level security concept traces request roles, grants, company claims, row policies, views and RPC execution. It distinguishes filtered rows from rejected writes and direct browser access from service-role API work. Global identity and private profiles have different policies; SQL and API now share live actor eligibility; resource predicates and execution privileges still differ. Route policy owns the privileged API boundary.
Functions and transaction boundaries
Section titled “Functions and transaction boundaries”The functions and transaction reference identifies selected atomic operations, their execution identity, locks, constraints and replay contracts. It separates grouped database changes from conditional updates, separate HTTP requests and provider effects. Number allocation is atomic within its own transaction; it does not make a later request atomic or guarantee gapless numbering. External outcomes require their own receipts and recovery.
Migrations and generated types
Section titled “Migrations and generated types”The migration procedure follows forward files, local schema/type/catalogue checks and populated upgrades through the guarded AX42 release. The CLI applies complete pending files independently; interrupted publication requires inspecting the actual ledger and correcting forward. Schema delivery retains the wider application-compatibility responsibility.