supabase-js VS pg_cron

[Edge Functions] Custom domains and vanity domains support for Edge Functions. PR

First of all, the code you provided is not directly supabase, but is whatever is provided from the javascript library. The auth part is then redirecting to the gotrue-js library, and as seen here [Gotrue-JS#L238] it returns a `Promise` and that specific type is declared here Where we see it could be two return types. ```ts | { data: { user: User | null session: Session | null } error: null } | { data: { user: null session: null } error: AuthError }

Next up, Supabase released v2 of their JavaScript client library (supabase-js), which brought with it a number of developer experience type improvements, and streamlined how we use some of the API's. A number of methods were also deprecated in this new release, which we'll cover later in this guide.

We install the Supabase client library and also Chakra-UI which we will be using to build our React components.

The last part is the easiest as we simply need to connect Supabase to our Ionic app and call one function. Get started by bringing up a new Ionic app and install the Supabase JS client:

Under src/lib I have a .ts file where I create a supabase client inside.

First and foremost, the language and framework – Typescript & React. Typescript is a must for a project of this size. It provides safety and peace of mind as I iterate quickly to solve bugs and add new features. React is a by-product of the next two things I will mention, Next and Remix. Both of these are higher abstractions on top of React and supply incredible tooling to build fast server side rendered applications. Picking one or the other was driven by my database and auth provider, Supabase. I could have tried to make it work with Remix, but there was already an authentication helper for Next from the Supabase community so I decided on Next. Still using Remix for this current website since I do love Remix so much.

Have a look at https://postgrest.org/en/stable/. They do something in this direction and e.g. supabase.io uses them. Their approach is, if you have a database you have a REST API.

[Postgres Extensions] pg_cron 1.5.2 (new projects only) now supports sub-minute schedules. PR

(Your PostgreSQL installation might already have pg_cron available, but if not, you would need to install it)

I’d set up citusdata/pg_cron in 14, so I’ll need to set that up in 15 as well.

Functions can be executed via a database query or on a regular schedule. Trigger functions are a special type of function that are covered in a previous article. They provide a way to execute an action based on a database event.

* extraction and loading: the psql-http PostgreSQL extension which is available in Supabase (but not all services like AWS RDS). Not sure how it works with OAuth but something to look into. * automation: use pg_cron to automate the ingest. * transformation: leverage Postgresql JSON functions.

A low-level alternative is using a PostgreSQL-side facility like https://github.com/citusdata/pg_cron - this, however, requires installing a PostgreSQL extension.

If you just want scheduling queries, you can use this https://github.com/citusdata/pg_cron