hgzimmerman / diesel_test_setup Goto Github PK

The non-postgres tests may need to be behind feature flags to prevent the tests from failing in the environment where this is usually developed (another project that this project is a submodule of)

At least in the Readme, and ideally in a dedicated directory.

This would eliminate some of the ambiguity in dropping a pool, at a minor expense to ergonomics.

The bad case currently is that someone doesn't assign the tuple returned by the setup functions.
This causes the tuple's children to be dropped in reverse order, causing an error when the Cleanup is dropped first.
By putting both the pool and cleanup in a structure, the drop order should be enforced.

The library seems very useful, and as you say in the README, potentially feature complete.
Any plans to publish to crates.io?

I'm reasonably confident that the current strategy works fine for MySql in exactly the same way as Postgres, while I question this library's utility for Sqlite.