Prioritized list of issues and missing features for me

[leio]

@carllerche suggested to make a meta-issue for things in priority order for me, so here we go. Priorities might shift and other things found added over time

Hard blockers for going live on production

• Toasty connection pool doesn't recover from a database restart #678
• toasty-driver-postgresql: Missing TLS support #660
• toasty-driver-postgresql: Unable to use some passwords due to percent-encoding #661

Semi-blockers

• Missing feature: Native PostgreSQL enums #641 - would be nice to introduce soon needed enums to database properly, instead of text or int fields with a need to migrate later
• toasty-cli: MigrationPrefixStyle::Timestamp prefix style is not honored #652 - I think I prefer timestamp based prefix (they should allow parallel work branches that both do migrations easier), so would be good to get that working before I re-do the non-local databases with toasty (as I can still regenerate the migrations from scratch until then with lower effort)

Various annoyances

• toasty-cli: Generated migration don't have a newline at EOF #654 - not really a priority at all, but very easy to fix up to not need manual fixes after migration generation (could do a PR myself, but won't be able to set up a toasty git testing for a while to get to it)
• Design: Foreign key constraints #366 - lack of proper foreign keys is not good for data consistency, I don't care too much about the ON UPDATE and ON DELETE behaviour configuration, as much as just making it impossible to store a fkey to something that doesn't exist
• toasty::create! should support struct field init shorthand (compilation broken after rustfmt) #649 - already fixed, just waiting for a release to remove workaround
• Add debug and trace level output using tracing in the engine #254 - would be good to at least easily see all the SQL queries toasty does, as to validate the code (and toasty) I'm writing easier; right now need to resort to temporarily tweaking local postgres config and restarting it, instead of just a RUST_LOG or application config change
• feedback on updates #456 - no RETURNING support for straight UPDATE calls is annoying when using a capable database and makes for extra database roundtrips
• Support soft deletion of models #462 - Annoying to have to hand-code this, but used to having to do it
• toasty-cli: Generates unnecessary UNIQUE index on primary key #653 - another one that means manual fixes on migration files when creating new tables; not making any more new tables soon, so liveable
• Missing feature: Server-side check constraints #644 - data consistency; some might be covered with an automatic CHECK on enums with payloads variant storage coilumns being added (currently isn't afaik)
• Missing Use Case: Upsert #422 - for current project can live with a manual SELECT + UPDATE or INSERT for the time being in a single usage case; the usage is the "Replacement" kind
• Implement Migration CLI Commands (migrate:generate, migrate:up, migrate:down, migrate:status) #190 - I think a lot of that issue is done, but missing down support, which is very useful for local development
• Missing Use Case: Querying by PK via a trait for generic usage #645

Longer term future blockers

• Missing Use Case: Composite unique constraints #639
• Missing Use Case: Unique constraints with conditions #640
• Missing Use Case: SELECT ... FOR UPDATE / SKIP LOCKED #424 - ability to send own SQL might alleviate this as well to some extent
• Missing Use Case: DISTINCT / DISTINCT ON #425

Nice to have's

• Missing Use Case: Database column defaults #642
• Don't depend on the postgres crate #651 - unnecessary dep