-
We gotta put our cores into the DB so we can run dist-update without subtly changing all the actual things that are happening. related: we might need to version the asset bundle too...
-
> Yeh - I think we can move that way later without a problem. The idea would be to provide "breaking" vs "non-breaking" Schema changes to be version controlled. Mostly from [Snowplow's musings](https…
-
**Is your feature request related to a problem? Please describe.**
I would like to be able to use `cadwyn` without FastAPI.
**Describe the solution you'd like**
I can define schema versions a…
-
![Screenshot_20240526-205727_GitHub.png](https://github.com/ClickHouse/clickhouse-java/assets/4661021/fdf65a4b-ea15-4e55-a6ef-e84c67937494)
Why don't use versions like 0.6.0, 0.6.1, 0.6.2 for bugf…
-
I was recently pointed at https://begriffs.com/posts/2014-12-30-intro-to-postgrest.html, where Joe presented the core ideas that PostgREST was built on initially. From 8:30 on, he talks about schema-b…
-
Schemas change over time. We need to design a safe way for composers and displays to interop safely if their schemas are on different versions. We should also consider tools to help prevent unexpected…
-
**What is the requested feature?**
Add versioning to the XSD schema.
There are few ways to do it ([summary](https://www.xfront.com/Versioning.pdf)), more or less standard.
So I would like to open t…
-
When performing an update of Electric service (with new migration schemas for Postgres) + deploying a new Flutter app (that matches new schemas), some app users will still have the old version of the …
-
At least locally for me, when I run ./test.py --mode=dev I see quite frequent failures of test_group0_schema_versioning.
For example:
```
=================================== FAILURES ============…
-
### Feature request
The schema of a source is set on creation. As the upstream schema changes, Materialize either tolerates these changes or puts the source in an errored state, but doesn't explicitl…