João Oliveira
João Oliveira
Hi @ankhers , I looked at this again today, but the arguments referred on https://github.com/rust-db/refinery/issues/83#issuecomment-620781813 persist, do you have an alternative?
yeah, I have said that previously but this feature has had a significant demand. I agree, having the cli generate the migration needed for each db seems the cleanest solution,...
> Before I continue with my PR. I just realized that if I have two migrations, 1 and 2, that if migration 2 gets applied BEFORE 1, then 1 will...
I see, yeah maybe that makes sense to implement after this, we can discuss it on another issue if you want. thanks
Hi, and thanks for your interest! >There isn't really a workaround from what I can tell. I can't hardcode the path to the project migrations folder inside this package, since...
Hi, and thanks for your interest. So when we first created refinery it was for relational databases, therefore the `Transaction` and `Query` traits. That being said, support for NoSql databases...
No worries, If you want to give it a try and have any questions I am on the Rust discord!
> I think the "Query" side could work with Mongo with a very similar API after just changing "table" to "document" or "doc" and allowing Mongo-specific types like ObjectId and...
following the proposal: > A user could create their QUIC implementation’s concept of a Connection, and then pass that to h3. This is a similar design to h2, which asks...
I submitted a PR with it back then https://github.com/tokio-rs/mini-redis/pull/32/