-
There are broadly two approaches we've considered:
1. **`impl sqlx::Encode/Decode` for all the important types.** This doesn't work transitively - if my parent struct is composed of fields that are a…
-
Due to D3D8LTCG's OOVPA signatures using two separate versioning which is understandable. However, the signatures with version "1024" appear are not always in 3911's database. Which I had noticed and…
-
https://github.com/CodaProtocol/coda/pull/3439 added `Persistent_frontier.Database`, which is currently unversioned. The database already has the concept of a version baked into it (storing a version …
-
## Add a migration generator
add something to automatically handle database migrations and versioning.
-
The Shopozor underlying database is taken from `saleor` project. In particular, it isn't provided with versioning. For example, when a Producer modifies a Product, we would like to be able to have a c…
-
I'm wondering if anyone knows the motivation for the disable-versions flag for the b2 backend?
Why would you ever *not* want disable-versions enabled?
If you have enabled version tracking in bac…
-
Have you given any thought to database versioning? I haven't done this in CI before, so I'm open to anything. There's this library that seems like it might do the trick: http://codeigniter.com/wiki/DB…
-
And yes, we will need some good versioning scheme to deal with database schema compatibility issues like this.
Added to the roadmap #737
_Originally posted by @victordibia in https://github.com/mi…
gagb updated
7 months ago
-
Very well done and lovely project! thanks
We thought may be to provide access to datasets you provide via https://github.com/datalad/datalad/ (based on git/git-annex). Here is e.g. a sample git/an…
-
As per #18, adding this separately so these should be able to be converted to issues independently, then closed nicely with PRs.
# Initial Release
## Features
- [x] #27
- [x] #28
- [x] Pre…