tianzhou

Congrats on the launch, good project name and glad to see new project trying to address the classic schema migration problem.

FWIW, I built pgschema https://github.com/pgplex/pgschema which is a declarative approach to manage this.

I see this as the same argument in old days where Harvard law school banned computer in favor of the typewriter https://x.com/stevesi/status/2075994207508922406

What I would argue is knowing what topic to write is more important, and I am confident if you throw this particular question to AI, the response would be much worse.

Author here. I did use AI to assist writing. The way I do it is I feed all my past writings (around 200+ posts) to the AI and let it record my style.

I research the topic, lay the outlines and let AI write it. Then I further refine section by section with a combination of AI and manual editing).

What you have pointed out is valid and it helps me to improve the process. And I have edited the post based on your suggestion.

As a non-native speaker and engineer with 15+ database development experience, I think I will continue to use AI to assist writing (I rarely use AI if I write in my native language). This post still takes me almost an afternoon to finish, but without AI, it will take me much more time.

Good stuff. I added to the latest star-history.com issue https://www.star-history.com/blog/ai-ui-irrelevant

If someone is looking for a more comprehensive coverage for Postgres, please check out https://github.com/pgschema/pgschema.

I built this last summer and thought it was fairly complete. And it turns out I was naive. 6 months later, I have resolved ~100 issues reported by the users.

Appreciate the Bytebase shoutout! Skeema has definitely been an inspiration.

Author here — I nearly overlooked this in the changelog. Definitely my second favorite feature (uuidv7() is tough to beat)

I ask Manus to write a script to demo my CLI tool and use asciinema to record it. It's perfect

Whole process: https://www.pgschema.com/blog/demo-with-manus-and-asciinema Replay: https://manus.im/share/8fEln1OzxpnsRSU1PnHweG?replay=1

Author here. To put it simply, my bank account doesn't have 3 commas mate.

https://x.com/mitchellh/status/1964785527741427940

Check out Bytebase which handles all human-to-db operations (schema change, ad-hoc change, ad-hoc query). Disclaimer: I am the co-founder.

While database tools may not grab headlines like high-profile data infrastructure, they are equally indicative of the industry’s momentum.

We have been building such a tool as well, please check out https://github.com/bytebase/bytebase

https://www.bytebase.com/sql-editor/ with data access control, dynamic data masking.

This post addresses the data migration specifics well. Besides, there is the part about scaling the organization to deploy database migrations. We've built a project https://github.com/bytebase/bytebase to address this.

From the stored procedure Pro clan:

1. Some applications can't tolerate the roundtrip latency, so the typical way is to put the business logic inside the stored procedure.

2. DBA wants to guard the database.

(Bytebase co-founder) Bytebase implements this https://www.bytebase.com/docs/change-database/synchronize-sc...

>> I really wish someone will implement DB Projects (dacpac) for Postgresql

Bytebase did https://www.bytebase.com/docs/change-database/synchronize-sc...

Combining the best of Google Slides and Apple Keynote

Quite a few folks are working it actually https://star-history.com/blog/text2sql

We have been building https://github.com/bytebase/bytebase for 3+ years. You can think it of as GitHub/GitLab for SQL changes, with integrated GitOps, code review and deployment.

You can further check out this tutorial to get a feel of our GitOps solution

https://www.bytebase.com/docs/tutorials/database-change-mana...

Architecture-wise, Postgres is more extensible. Another reason is licensing. Both contribute to a viral ecosystem.

https://www.bytebase.com/blog/postgres-vs-mysql/

Cisco or Okta

FWIW, we at bytebase building the batch change feature to make this less painful https://www.bytebase.com/docs/change-database/batch-change/

We are also building Bytebase, which enforces the change review process for such operations

We have been working on bytebase (https://github.com/bytebase/bytebase) for 3+ years to address this. With a change review workflow, environment propagations, and try not to disturb the dev flow if possible.

+1. We have been working on a schema migration tool called Bytebase for 3+ years. And we follow the similar principles.

FWIW, we are building a CI/CD solution snowflake https://www.bytebase.com/docs/tutorials/database-change-mana...

Modern Snowflake Stack can be thought of as an implementation of Modern Data Stack

As a frequent code reviwer, the CSS seems to be off.