ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I'm designing a schema migration for a DuckDB database (assuming a recent stable release, e.g. 1.x) and need to add a non-nullable-style column to a large existing table. My understanding from the documentation is that ALTER TABLE t ADD COLUMN c INTEGER DEFAULT 0 records the default as schema metadata, but existing rows still read as NULL until an explicit U
Scenario A Filament form uses a Repeater field with a default closure that pre‑populates a row. After upgrading the application, the database migration that creates the repeater’s underlying table is rolled back due to a failure. The form still renders, but no rows appear, suggesting the default closure is not re‑executed. Constraints • Filament 2.x or newer
JSON Schema offers two documented mechanisms for fields that downstream processing expects to always exist: the required keyword, which fails validation when a property is absent, and the default keyword, which supplies a fallback value. Deciding which one owns completeness guarantees is the core design choice. Under the draft-07 through 2020-12 meta-schemas
duckdb
filamentphp
json