![]() We recommend using these wherever possible. You can use these for all browser and application interactions. The Data APIs provide programmatic access and have built-in connection pooling.Under Connect to your database directly, copy your Connection string.You can find the direct connection string in the Database settings inside the dashboard: If you need an ipv4 address, use the connection pooler instead. By default, this connection uses ipv6, which isn't supported by all network providers. You can use a direct connection to connect directly to your Postgres database. Under Connect to your database via connection pooling, copy your Connection string. ![]() You can find the connection pool config in the Database settings inside the dashboard: Supabase's connection pooler also supports ipv4 out of the box. Realtime: listen to database changes over websockets.Įvery Supabase project comes with a connection pooler for managing connections to your Postgres database.Ī connection pooler is useful for managing a large number of temporary connections - for example, if you are using Prisma, Drizzle, Kysely, or anything deployed to a Serverless environment (AWS Lambdas or Edge Functions).GraphQL: interact with your database through a GraphQL interface.REST: interact with your database through a REST interface.We provide several types of API to suit your preferences: These are the easiest way to get started if you are managing data (fetching, inserting, updating). Supabase provides auto-updating Data APIs. If you use the database connection string, see the GitHub discussion on how to prepare for IPv6. If you connect to your database using the REST and GraphQL endpoints, this doesn't affect you. Starting on January 26, 2024, direct database connections will start resolving to an IPv6 address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |