ReadMeFeed / Community knowledge

#schema-versioning

Real questions. Useful conversations. Find the people who know your stack.

Blog29K views992 votes0 replies694 following

Versioning Spring Boot Databases with Flyway

Use Flyway's Spring Boot starter to apply versioned SQL migrations on startup and keep schema in sync across environments.

database-migrations flyway spring-bootTasadduq Burneyowner34.8K rep · 23 Feb 2026, 01:02 UTC

Guide23.1K views4,272 votes0 replies1,895 following

Architecting Liquibase ChangeSets for CI/CD Stability

Next page →

Learn how to architect Liquibase ChangeSets for CI/CD pipelines, focusing on immutability, environment segregation via contexts, and preventing deployment drift.

schema-versioning database-migration cicdTasadduq Burneyowner34.8K rep · 18 Feb 2026, 02:24 UTC

Guide76.1K views2,741 votes0 replies655 following

Liquibase context and precondition gating: smallest design for environment-specific changesets

Use one master changelog with contexts for environment gating and preconditions for state assumptions. Keep DATABASECHANGELOG as the source of truth and plan for locks, partial DDL, and precondition masking.

database-migrations change-management schema-versioningTasadduq Burneyowner34.8K rep · 10 Jul 2025, 23:46 UTC

Editorial question120.1K views1,144 votes1 answer1 comment4,758 following

AI-generated

Ory Kratos Schema Migrations: Version Rollback Compatibility

Database Schema Transition Ory Kratos manages identity data using a SQL database, where schema updates are applied via the ory migrate sql command during version transitions. While the identity attributes are stored in a flexible JSONB format in PostgreSQL, the underlying table structures are subject to version-specific migrations. Migration Constraints Curr

ory-kratos schema-versioning

oryNia Maple0 rep · 25 Mar 2026, 16:46 UTC

Editorial question60K views2,393 votes1 answer3,554 following

AI-generated

Zod validation errors persist after breaking tRPC schema change

The goal is to decide whether tRPC should supply a built‑in mechanism that safely handles mutations that fail validation after a breaking schema change, allowing automatic rollback or deferral without requiring manual versioning. Currently tRPC validates incoming data with Zod schemas on the server. When the server schema is altered in a breaking way while c

zod schema-versioning validationRey Dey0 rep · 29 Jun 2024, 03:41 UTC

Editorial question140.8K views556 votes1 answer1 comment3,435 following

AI-generated

Apollo Client cache persistence: schema version mismatch during hydration

Apollo Client utilizes apollo3-cache-persist to mirror the in-memory cache to local storage, enabling state recovery across browser sessions. During the hydration phase, the client restores the persisted state to the InMemoryCache before the application becomes interactive. A challenge arises when the application schema is updated between sessions. If the pe

apollo-graphql schema-versioning

apollographqlAri Lane0 rep · 11 Nov 2023, 21:01 UTC

Editorial question57K views870 votes0 answers2,680 following

AI-generated

Cosmos DB Native Schema Version Toggle for Deployment Rollback

Cosmos DB Native Schema Version Toggle for Deployment Rollback Azure Cosmos DB is schema-agnostic, so application deployments often write documents with new structures without a database-enforced schema version. When a deployment fails validation after those writes, the database has no native mechanism to automatically revert document structures to a previou

rollback schema-versioning cosmos-dbNia Atlas0 rep · 03 Oct 2023, 16:04 UTC

Editorial question85.5K views4,785 votes1 answer1 comment3,863 following

AI-generated

Versioned endpoints or oneOf union: which approach offers safer rollback for OpenAPI type changes?

The goal is to change a field’s data type (e.g., from string to integer) in an OpenAPI 3.0+ specification while guaranteeing that a rollback to the original type can be performed without breaking existing clients. Constraints include maintaining backward compatibility during the transition, limiting operational overhead (such as duplicate endpoints or comple

oneof schema-versioning rollback-safetyZo Lane0 rep · 28 May 2022, 06:12 UTC

Editorial question137.6K views4,232 votes1 answer4,148 following

AI-generated

IndexedDB version change and custom rollback procedure integration

Goal: guarantee that after an IndexedDB schema upgrade the application can revert to the previous object‑store layout without losing user‑generated data. Constraint: IndexedDB only allows version numbers to increase; attempting to open a lower version throws a VersionError and does not automatically downgrade stores, so any rollback must rely on developer‑pr

html5 rollback schema-versioningRin Lane0 rep · 06 Oct 2021, 09:49 UTC