Directly in the DB not receive the changes via websockets

[kurdin]

Hi guys, thanks for development of interesting project, trying to wrap my head on how is your system works.
I was playing with next.js example, and everything seems to be working as expecting except this claim from your Docs:

The beauty of listening to the replication functionality is that you can make changes to your database from anywhere - your API, directly in the DB, via a console etc - and you will still receive the changes via websockets.

After I edited users or todos table's data directly in DB I don't see any update or change events (in realtime) in the browser. Only if I reload the page I can see updated values from modified db. Am I missing something or misunderstood concept of the system from your Docs?

[inian]

Hello Sergey. You can use our realtime library to listen to changes. This library will capture realtime changes made from the API, directly via the DB, etc.

The dashboard in the browser does not update in realtime yet, but we are actively working on this :)

[kurdin]

@kiwicopple any plans to make GraphQL module for supabase, similar to postgrest ?

[kiwicopple]

No plans, since PostgREST has embedded resources. Is there something you are missing with PostgREST @kurdin ?

[kurdin]

@kiwicopple I like REST, simple and strange forward to create and use but GraphQL has a very nice and convenient features that makes it better for larger projects. GraphQL is hot, hype is out there and it's getting more popular among modern devs, it makes hire smart and progressive devs easy if your project has cool backend in GraphQL. But yeah, some projects just don't need it, REST still a king for regular data communications between UI (App, Web) and Backend (DB).

[kiwicopple]

Good feedback, thanks Kurdin - at the moment we want to keep our surface area a small as possible so that we can move fast, but we will definitely consider this for the future

[oskarer]

@kurdin If you're looking for GraphQL on Postgres check out Nhost