Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Building Production-Grade Web Applications with Supabase
  • Table Of Contents Toc
Building Production-Grade Web Applications with Supabase

Building Production-Grade Web Applications with Supabase

By : David Lorenz
4.5 (11)
close
close
Building Production-Grade Web Applications with Supabase

Building Production-Grade Web Applications with Supabase

4.5 (11)
By: David Lorenz

Overview of this book

Discover the powerful capabilities of Supabase, the cutting-edge, open-source platform flipping the script on backend architecture. Guided by David Lorenz, a battle-tested software architect with over two decades of development experience, this book will transform the way you approach your projects and make you a Supabase expert. In this comprehensive guide, you'll build a secure, production-grade multi-tenant ticket system, seamlessly integrated with Next.js. You’ll build essential skills for effective data manipulation, authentication, and file storage, as well as master Supabase's advanced capabilities including automating tasks with cron scheduling, performing similarity searches with artificial intelligence, testing your database, and leveraging real-time updates. By the end of the book, you'll have a deeper understanding of the platform and be able to confidently utilize Supabase in your own web applications, all thanks to David's excellent expertise.
Table of Contents (20 chapters)
close
close
Lock Free Chapter
1
Part 1:Creating the Foundations of the Ticket System App
5
Part 2: Adding Multi-Tenancy and Learning RLS
10
Part 3: Managing Tickets and Interactions
15
Part 4: Diving Deeper into Security and Advanced Features

Working with complex table joins

We’ve learned about joining related tables by using nested select strings (for example, fetching related comments in tickets), but with Supabase, you can do the following:

  • Resolve ambiguous joins, to avoid errors, explicitly
  • Rename joined tables on the fly
  • Create inner joins to only return data where related data exists
  • Combine the renaming feature with the inner join feature

Let me show you a few practical examples.

In our tickets table, we have two user references: created_by -> public.service_users and assignee -> public.service_users. I want to retrieve both user objects with a join. We do so by nesting the related table like so:

supabase.from("tickets").select("*, service_users(*)");

This will fail – since there are two pointers pointing to service_users, it will not know which one to resolve.

However, you can also resolve this another way, by declaring two explicit joins...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Building Production-Grade Web Applications with Supabase
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon