Settings and activity
11 results found
-
160 votes
An error occurred while saving the comment Scott Pierce supported this idea · -
77 votes
An error occurred while saving the comment Scott Pierce commentedI think that instead of exposing FTS directly, there needs to be a very clear way that we can gain access to the table creation and provide any options that we need. There are a growing number of postgres features and syntax, that we will need clear ways to access.
Scott Pierce supported this idea · -
8 votesScott Pierce shared this idea ·
-
12 votesScott Pierce shared this idea ·
-
8 votesScott Pierce shared this idea ·
-
1 voteScott Pierce shared this idea ·
-
88 votesScott Pierce supported this idea ·
-
6 votesScott Pierce supported this idea ·
-
9 votesScott Pierce supported this idea ·
-
94 votesScott Pierce supported this idea ·
-
64 votesScott Pierce supported this idea ·
Postgres's support for realtime queries isn't very efficient, and wouldn't scale well when used in a similar manner to firestore. It'd be nice if they offered a higher level form of this that would allow realtime updates in some form.
i.e. since they are making the queries for us in the graphql, as data is inserted, they could process it to see which active queries it effects and then notify the clients of changes.
This would be really nice, but probably too much of an ask?