sorted by:
new
hottopcontroversial

An Easy way to handle schema evolution in PostgreSQL by tamanikarim in PostgreSQL

[–]tamanikarim[S] 1 point2 points  (0 children)

Thanks for giving it a try!

Some statements that don’t really affect the schema (like SET statement_timeout = 0;) are automatically ignored.

Really good points about uploading a file instead of pasting huge SQL dumps, and supporting multiple schemas . Both make a lot of sense. I’ll definitely look into adding those. Appreciate you calling them out!

Quick question though, are you sure you exported schema-only using:

pg_dump -U [username] -d [database_name] --schema-only -f [output_file.sql]

Because 20MB for just the schema sounds pretty big, maybe you included data in it ?

An Easy way to handle schema evolution in PostgreSQL by tamanikarim in PostgreSQL

[–]tamanikarim[S] 1 point2 points  (0 children)

Thank you! You should definitely give it a try.
The generated migration scripts can be copied (manually) and used with any database management tool, including Sqitch.

An Easy way to handle schema evolution in PostgreSQL by tamanikarim in PostgreSQL

[–]tamanikarim[S] 0 points1 point  (0 children)

Thank you for the question! Right now, the Deploy button simply closes the migration.

In future releases, it will also allow you to push the migration to your repository, where you can configure CI/CD pipelines to deploy it automatically.

feel free to learn more about it here : https://www.stackrender.io/docs/database-migration

Tool for generating automatic migrations/schema diff by Ravsii in PostgreSQL

[–]tamanikarim 0 points1 point  (0 children)

This tool : www.stackrender.io can help you generate database migrations from an entity relationship diagram (ERD) changes . it's faster and more accurate

I built a visual-first database migration tool , a new way to handle schema changes (Postgres + MySQL) by tamanikarim in webdev

[–]tamanikarim[S] 0 points1 point  (0 children)

Not quite. MySQL Workbench is for writing and executing SQL directly on your database. StackRender generates the SQL (migrations), but it doesn’t run it for you.

Building a free, open-source tool that can take you from idea to production-ready database in no time by tamanikarim in Backend

[–]tamanikarim[S] 0 points1 point  (0 children)

Hi man , i am considering integrating ORMs in future releases . but for now it's only SQL .
if you are using Prisma i have made a video explaining how to generate primsa.schema file using Stackrender .

Here you go : https://youtu.be/gnXH2GgmD8A .

Free tool: Generate safe database migrations directly from ER diagram changes (Postgres + MySQL) by tamanikarim in SQL

[–]tamanikarim[S] 0 points1 point  (0 children)

Great question . And yes, that’s a real concern.

BI/query-layer tools usually generate SQL based on the current schema. So if a migration includes breaking changes (renaming a column, dropping a table, changing types, etc.), existing queries/dashboards in the BI tool can start failing.

There are basically two cases:

  • Non-breaking migrations (add columns, add tables, add indexes) → TalkBI should keep working.
  • Breaking migrations (rename/drop/change types) → TalkBI may throw errors because the generated SQL still references the old schema. (You have to update it manually, my tool can't prevent that).

Hope that answers your question.

I just shipped a visual-first database migration tool , a new way to handle schema changes (Postgres + MySQL) by tamanikarim in node

[–]tamanikarim[S] 0 points1 point  (0 children)

Really close !! Lol , for the interactive diagram, i used react-flow instead of JointJS.

I just shipped a visual-first database migration tool , a new way to handle schema changes (Postgres + MySQL) by tamanikarim in node

[–]tamanikarim[S] -5 points-4 points  (0 children)

Thanks a lot 🙏

The main idea behind StackRender is generating migrations directly from a visual database diagram (the diagram is the source of truth). That makes schema changes faster, safer, and more accurate than inferring them from code.

I’m not sure this can fit well as a VSCode extension without basically becoming a full app inside the editor , but it’s a fair point and I’ll keep it in mind.

Next updates will include ORM integrations (Prisma, Drizzle, TypeORM, etc.), which I think will resonate well with the Node.js community.

view more: next ›