Dmitrii Aleksandrov
Dmitrii Aleksandrov
Turns out, type names are their own thing, kinda like column refs. Both are more complicated than "just" schema-qualified names (like tables and functions): https://github.com/SeaQL/sea-query/pull/922#issuecomment-3179934497 🫠
The initial fix has been merged and will be released in SeaQuery 1.0.0 (SeaORM 2.0.0). But the current design of `TypeName` isn't necessarily the final one: https://github.com/SeaQL/sea-query/issues/954
Yeah, I've already encountered this same issue: #2225
#2367 has been merged today. Is your issue resolved on the current `master` ([`88f4bf1`](https://github.com/SeaQL/sea-orm/commit/88f4bf1b9df88cf80fb309590b88ccb1db43b01b))? You need to disable `default-features` on `sea-orm-cli` and activate only the needed DB backends
Generic support for custom `FROM` clauses would be useful and consistent with other escape hatches like [`Expr::cust`](https://docs.rs/sea-query/latest/sea_query/expr/struct.Expr.html#method.cust). It's a bit weird that methods like [`SelectStatement::from`](https://docs.rs/sea-query/0.32.3/sea_query/query/struct.SelectStatement.html#method.from) accept an [`IntoTableRef`](https://docs.rs/sea-query/0.32.3/sea_query/types/trait.IntoTableRef.html) parameter, where...
Hmm, I've just noticed that MySQL index hints are [already implemented](https://docs.rs/sea-query/0.32.3/sea_query/extension/mysql/trait.MySqlSelectStatementExt.html). It's right there in [the search](https://docs.rs/sea-query/0.32.3/sea_query/extension/mysql/trait.MySqlSelectStatementExt.html?search=index)
Yeah, this always seemed weird and unergonomic to me. Also, `get_` prefixes are uncommon in Rust, they only add noise IMO.
@piaoger, could you open a separate issue with details about panic conditions? This issue is about API style
> Workarounds > 🤷♂️ I believe, it should be possible to [patch](https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html) `rsa` to a compatible version with a security fix or patch `sqlx-mysql` to a compatible version that replaces...
> The Rust enum should match the order of the Postgres enum. Actually, enum ordering differs across databases. See #2132. For SQLite, SeaORM emulates enums as strings and SQLite compares...