Bryce Plunkett

**I also ran into a similar issue on preact-cli 3.3.3, but the following steps seemed to fix it:** 1. I upgraded to preact-cli `3.3.5`. I got a new error message...

> Sorry, are you saying the error message changed upon upgrading preact-cli to v3.3.5 / past 3.3.3? > > Makes sense that Firebase may not be suitable in Node when...

>This should be an option in pg-schema-diff. It seems that SET statements are not included in the diff plan, so the plan validation fails even when I tried setting check_function_bodies...

Rough materialized view support has been added. I still need to add support for indexes...and various "quality of life" features.

I might be a bit confused with this one. Could you give an example of the diff of your schema, the hypothetical command to plan your migrations, and the expected...

I strongly recommend skipping plan validation (it's a flag). pg-schema-diff inherently relies on being to diff(empty db, your source db schema). So if your source db contains any schema objects...

It doesn't use pg_dump because many hosts don't have pg_dump or support for libpq. I'd be open to adding support it for hosts that have it installed.

It should. Do you have the SQL for reference, pg dump of your schema, and the command you are running to generate the diff?

Okay, I was mistaken. We do not support stored procedures. I was under the impression that function support == stored procedure support (and that stored procedures are just syntactic sugar...

I was looking into this today! Yes, I can try to get it done this week. I have a prototype for a continuing refactor I'm also working on, but I...