bitfl0wer
commented
3 months ago Going forward, the supported Database flavor will be PostgreSQL. Supporting many different SQL flavors is nice, but taking full advantage of the features one SQL flavor has to offer is better, in my opinion. "A Jack of all trades is a master of none", and so on.
Issues that remain here are:
- [x] Removing nested structs which are
Json<T>in favor of foreign keys/breaking out everything into its own tables, where it makes sense. - [ ] Related to above: Rewrite
CREATE TABLEstatements as well asquery!()calls to query nested struct tables as well, where it makes sense. - [x] Support unsigned integers in PostgreSQL by either using
#[sqlx(try_from = sqlx::types::Decimal)]or by creating wrapper types which translate Rusts unsigned integers into Postgres' DECIMAL/NUMERIC types while guaranteeing that the DECKMAL/NUMERIC loaded from a table is not out of bounds for the selected integer size
A sizeable amount of sysadmins prefer PostgreSQL over MySQL/MariaDB. As such, Postgres should be supported in symfonia as well. This could be accommodated for by using the
sqlx::Anytrait instead ofsqlx::MySqlthroughout the codebase.Changes are being made in chorus to support sqlx::Any, as well as updating sqlx to version 0.8.0.