20 ms·

I'm very glad to see work being done on db bindings, but until migrations reach the level of django/active record, I won't be using postgres + node.js seriously

• albertgao 6y ago
  no worries, it's their goal :)
• albertoperdomo 6y ago
  I'm with the product team at Prisma. Prisma Migrate is different from ActiveRecord migrations (which are very familiar with) because the DB schema is state-based. The Prisma schema file acts as source of truth and the DB schema will be migrated to match it. Can you elaborate on what you would perceive as reaching the level of Django/ActiveRecord? I'd be interesting in specific aspects/items.
  • dirkc 6y ago
    That sounds great! I'm not super familiar with ActiveRecord, but I use Django migrations regularly. For me the things that stand out are 1. a declarative model - ie. defining the db schema rather than the migrations 2. auto generated migrations with the ability to customize 3. integration with tools for deployment and testing You probably have a much better idea of the landscape, but reach out to Andrew Godwin [1], he wrote south and then rewrote it to become django migrations. [1] - https://www.aeracode.org/ https://www.aeracode.org/