Is as _ needed for templating string data, and x as "x: X" needed for returning data when using enum in PostgreSQL?

[alissa-tung]

Hello, I am trying to create some Rust enum to match the ones in PostgreSQL.

CREATE TYPE "project_status" AS ENUM ('PREPARING', 'NORMAL', 'ARCHIVED');

#[derive(Clone, Copy, Debug, sqlx::Type)]
#[sqlx(type_name = "project_permission")]
#[sqlx(rename_all = "UPPERCASE")]
pub enum ProjectPermission {
    Read,
    Write,
    Admin,
}

when using query! macro, when returning data, without as won't work

        let xs = sqlx::query!(
            r#"
select
    "userId", permission as "permission: ProjectPermission",
    tid, email, "displayName", "profilePictureUrl"
from "UsersOfProjects"
join "User" on "User".id = "userId"
where "projectId" = $1
"#,
            project_uuid
        )

and also for templating data

                sqlx::query!(
                    r#"
insert into "UsersOfProjects"
    ("userId", "projectId", permission)
values
    ($1, $2, $3)
"#,
                    uid,
                    project_uuid,
                    project_permission as _
                )

won't sqlx can figure out what type is by type_name? Or I am doing something wrong

Thank you

---

according to the document of query! macro,

Force a Different/Custom Type
Selecting a column foo as "foo: T" (Postgres / SQLite) or foo as foo: T (MySQL) overrides the inferred type which is useful when selecting user-defined custom types (dynamic type checking is still done so if the types are incompatible this will be an error at runtime instead of compile-time). Note that this syntax alone doesn’t override inferred nullability, but it is compatible with the forced not-null and forced nullable annotations:

Using expr as _ simply signals to the macro to not type-check that bind expression, and then that syntax is stripped from the expression so as to not trigger type errors.

Seems the two ways disable compile time type checking?

---

#2149

#2588