Why Doctrine ORM Skips Updates After flush(): A UnitOfWork Diagnostic Guide
Doctrine flush() with no UPDATE? Check if your entity is managed, inspect the UnitOfWork change set, and verify mapping and transaction boundaries.
Loading…
ReadMeFeed / Community knowledge
#changeset
Real questions. Useful conversations. Find the people who know your stack.
Why Ecto.Changeset.cast/3 Is Your First Line of Defense Against Bad Input
Ecto.Changeset.cast/3 whitelists permitted fields and coerces types, blocking mass-assignment attacks by construction — but it silently drops unknown keys and does no business validation. Here's how to use it well.
ectoLiquibase rollback fails with missing rollback definition after addColumn changeset
Rollback aborts after a deployed schema change I have a changelog where one changeset adds a column with a default value to an existing table, and a later changeset builds on that column. When I run a rollback command targeting the earlier changeset, Liquibase aborts and reports that no rollback was defined for the changeset, leaving the schema untouched. My
Liquibase 4.0: Recovering Safely from a Failed Upgrade
Goal Determine how to roll back a database that has experienced a partial changeSet failure while preserving data integrity. Constraints Liquibase records a changeSet in DATABASECHANGELOG only after a successful run; a failed changeSet is omitted. Rollback relies on timestamps; if a changeSet failed mid‑execution, its timestamp is missing, making the target
Changelog files + databasechangelog table: Does Liquibase treat id/author/file path as unique?
In multi‑file Liquibase projects the same id and author can appear in several changelog files. The databasechangelog table records each execution, but the uniqueness rule that triggers duplicate warnings is not clearly documented. Historically, some releases logged a warning when the same id and author were found in more than one file, yet the later instance
Does Ecto.Changeset.cast provide a global configuration for empty_strings_to_nil?
When processing form data or API requests, Ecto.Changeset.cast/4 allows developers to convert empty strings to nil using the empty_strings_to_nil option. This prevents blank strings from being persisted in database columns where NULL is the preferred representation of missing data. Currently, this behavior is typically managed on a per-changeset basis. In la
Liquibase changesets ↔ PostgreSQL: Pagination of large queries
Goal During a data‑migration Liquibase changesets often need to process millions of rows. The objective is to use a pagination strategy (LIMIT/OFFSET or cursor‑based) within a changeset so that each batch fits comfortably into a single transaction and does not lock the entire table. Constraints Liquibase’s <sql> and <sqlFile> tags accept raw SQL,
liquibaseLiquibase rollback halts at changeset missing rollback logic
Goal: Determine whether Liquibase halts a rollback when it reaches a changeset that has no explicit rollback block, and whether changesets already reversed in that same rollback range remain rolled back after the halt. Constraint: Liquibase auto-generates rollback SQL only for a limited set of change types. Raw SQL, drop operations, and data changes usually
Does Liquibase Support a Configurable Timeout for Whole Changeset Execution?
The goal is to allow a Liquibase update operation to be halted after a user‑defined duration, ensuring that any partially applied changeset can be rolled back or left in a known state. Currently Liquibase executes each changeset within a database transaction when supported, but it does not expose a timeout property for the whole update; users must rely on JD