Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

this would depend on your frontend setup?

nothing's stopping you from making state changes before firing your network request

or you could integrate something like rxdb

Except it's not guaranteed eventually. With a Firebase app I can implement a todo system where the user can add and delete before a network request ever fires, say with no/poor internet. With a rest only approach I need to wait for the insert to complete before allowing the user to delete.

In order to make the app really feel realtime

there's nothing that prevents you from editing your state and async sending a network request

or even adding it to some queue to send later

Only the database enforces relations, and generally has validation.

Even the IDs are generated on the database side using auto increment

sounds like you're looking for an offline db

Yeah sorry for the confusion. My question was if supabase will support realtime sync like Firebase does?

Does subscribing to table updates not do what you're looking for? https://supabase.com/docs/reference/javascript/subscribe

That's for reading, sync would be more for writing.

I think the confusion is coming from you using the name "realtime" which is the subscription concept for supabase.  You can use realtime to sync reads or writes to a table back to your app.
But I think you are asking for the caching the firebase client does using local storage/indexed db.  Supabase does not support anything like that.

I'm using localforage to do though a similar thing

I cache reads and update cache with writes.  I have a queue in the localforage storage for writes if off line and execute them when back online.  I use a subscription on a status table to detect online/offline and for updates to table if from another device.  My app though only has a user able to access their own data, so only worried about them updating their  own data on other devices.  Also like you point out I'm not worried about the eventual RLS check for the cached writes, because the RLS is only to make sure it is that user's data.

Ok cool, thanks. I had no heard of localforage

There are many local database utilities, I just like it's simplicity, that it uses indexedDB and that I can easily have a separate clearable "cache" for writes, data read by type and queries and clear anyone of them without clearing them all.

It is only one tool though.  You still have to write all the logic to deal with offline and updating, clearing etc.  It is just part of the solution I used.

Oh it also stores files and images as js file objects so I can even queue those for later update to supabase.

If you don't need to worry as much about "offline" adaptability, I would recommend using something like `reactQuery` with optimistic mutation updates. I believe this will map well with the write syncing you're looking for.

How do I update password with confirming old password?

Your question is a bit vague.   If you are asking about ways for user to reset their password with auth, I believe the only option is reset link.  I've not spent much time messing with auth though.

Thanks for your reply. I apologize for not clearing my query/question. Now let me clear what I am looking for.

This is the profile settings page where logged in user can update their password.  I can simply update password via

```js
await supabase.auth.update({password: 'new password'})
```

But I am looking for a solution for verifying current password before updating user password.

Yeah, that was my guess on what you wanted.  If there is a way, I'm not familiar with it as I don't think there are any other auth commands that deal with password besides signin/up.  I guess it might be possible to write a function to access the encrypted password in the table and compare it, but I do not know if the salt/key is available to do that.  Maybe someone else will jump in.  Supabase uses gotrue so you might google that.

You would have to use a bcrypt library and use the default hash cost, here is the code form gotrue that supabase uses for its hashing https://github.com/supabase/gotrue/blob/master/models/user.go#L244-L250

Whatever you do, don't run this in the client, do this in a server side call.

I would recommend creating an api route that takes in a current password and new password, logs in to an account, and then changes the password if the user is authenticated using the update query

If you're building with next you could accomplish either my or silentworks solution with the api routes sdk and have it run on vercel easily

I also try this technique before. But sadly when I put wrong password to login method I have been logged out.

I've given a solution that should get the job done

restarting the server resolved the problem

but now, when I use the supabase js client, it throws an error, that wasn't before: `message: 'FetchError: invalid json response body at https://id.supabase.co/rest/v1/tableName?select=* reason: Unexpected token < in JSON at position 0'`

For the "inactivity" period on free supabase postgres DB, my application purely uses the `postgres` user to make direct PG connections, it does issue reads and write into the DB continuously, but I don't use the supabase rest API to access, so does raw DB activity count towards the inactivity?