Benjie

> Yikes, that's a pain. To make another completely off-track suggestion, I wouldn't be opposed to giving more write access to graphql-wg and consolidate the list of RFCs there. Lower...

Please do not submit AI-generated issues; if you're tempted to do so, please instead submit the prompt that you would issue to the AI and allow me to run it...

I'm assuming the prompt was something along the lines of "Please fill out this issue template requesting support for Bun.SQL and make a compelling argument for its usage". Please correct...

That's okay; those features are optional. Notice can be skipped over (just return empty array). Lack of listen/notify means that users will not be able to use Postgres pub/sub for...

I'm not entirely sure how to handle the lack of listen/notify; but the simplest method is probably just to return a rejected async iterator any time the person tries to...

If that serves your needs, great. But I would not encourage that approach to working around a lack of LISTEN/NOTIFY - just don't use LISTEN NOTIFY if you don't support...

Thank you for your pull request. Since I am not familiar with Elysia I will not be merging this before the 5.0.0 release, and with the winter holidays coming up...

What is Railway? No, you should not drop in production. There are instructions on deploying to Heroku here: https://github.com/graphile/starter#deploying-to-heroku Deploying to other environments would have similarities.

After following the setup instructions following the link above, on every release you should run: ``` yarn db migrate ``` as done in our Procfile for Heroku: https://github.com/graphile/starter/blob/0b68eabc8ed414029594f40ca7bdcd8b46e17cb6/Procfile#L3

```sql create table node_id (id serial primary key, node_id int); insert into node_id (node_id) values (null), (1), (2); ``` ```graphql { allNodeIds { nodes { id nodeId } } }...