Generate Custom Types for certain Columns from tables

[DhineshKrishnan2]

I have a enum type defined in my column of a table.when i use diesel_ext > src/models.rs I ran into a issue of {MyEnumType} is not recognized. Please feel free to expand the HashMap.This could provide good hints: https://kotiri.com/2018/01/31/postgresql-diesel-rust-types.html is there any way to allow the custom types.There's no problem in generating schema as it finds the enum and creates some Empty structs for enums.Later i can use diesel-derive-enums for working with enums

[draagc]

The workaround I've used is the --map option to specify which rust type it is (which is itself, generated by diesel print-schema) like so: diesel_ext --map MyEnumType MyEnumType. This could be done automatically, might work on this and raise a PR when I get some time.

[abdulrabbani00]

Hey I am seeing the following error:

Array<Nullable<UserPosition>> is not recognized. Please feel free to expand the HashMap. This could provide good hints: https://kotiri.com/2018/01/31/postgresql-diesel-rust-types.html
Array<Nullable<RealTimeUserPosition>> is not recognized. Please feel free to expand the HashMap. This could provide good hints: https://kotiri.com/2018/01/31/postgresql-diesel-rust-types.html

I have the custom types written out:

use diesel::sql_types::Decimal;

#[derive(diesel::query_builder::QueryId, Clone, diesel::sql_types::SqlType, Debug)]
#[diesel(postgres_type(name = "real_time_user_position"))]
pub struct RealTimeUserPosition {
    pub bank_address: String,
    pub is_asset: bool,
    pub amount: Decimal,
    pub value: Decimal,
    pub emissions_outstanding: Decimal,
    pub shares: Decimal,
}

#[derive(diesel::query_builder::QueryId, Clone, diesel::sql_types::SqlType, Debug)]
#[diesel(postgres_type(name = "user_position"))]
pub struct UserPosition {
    pub bank_id: i32,
    pub is_asset: bool,
    pub amount: Decimal,
    pub emissions_outstanding: Decimal,
}

And I running:

diesel_ext generate model \diesel_ext generate model \
  --derive "Queryable, Debug, Identifiable" \
  -I "crate::db::schema::*" \
  -I "crate::db::custom_types::{UserPosition,RealTimeUserPosition}" \
  -m '{Array<Nullable<UserPosition>>}' '{Vec<Option<UserPosition>>}' \
  -t \
  > src/db/db_models.rs

I've tried various combos of this but no luck. I see the following in my file:

    pub positions: Vec<Option</* TODO: unknown type Array<Nullable<UserPosition>> */>>,

Please let me know if there is a workaround here.

[draagc]

@abdulrabbani00 Just the enum types need to be added to the HashMap. Also realised that my example was not formatted ideally as the braces should not be included. In your case, the following should work:

diesel_ext generate model \
  --derive "Queryable, Debug, Identifiable" \
  -I "crate::db::schema::*" \
  -I "crate::db::custom_types::{UserPosition,RealTimeUserPosition}" \
  -m 'UserPosition UserPosition'  \
  -t \
  > src/db/db_models.rs

[abdulrabbani00]

Thank you very much for the swift response. But this is not an enum type this is a custom type. I see the following error in the console:

Array<Nullable<UserPosition>> is not recognized. Please feel free to expand the HashMap. This could provide good hints: https://kotiri.com/2018/01/31/postgresql-diesel-rust-types.html

And I see this inline:

    pub positions: Vec<Option</* TODO: unknown type Array<Nullable<UserPosition>> */>>,

[draagc]

@abdulrabbani00 From the point of this application it doesn't really matter what database type it is. Everything generated by diesel_cli_ext is based on the schema generated by diesel cli. The pub mod sql_types in the schema contains all the custom types, which as far as diesel is concerned (at least with PostgreSQL) is everything excluding the built-in types, including enums, domain types and types introduced by extensions such as Ltree for example.

diesel_cli_ext at the moment does not handle these automatically, you can look at parse.rs for the HashMap that contains all the supported Diesel types; for now you will need to specify each of them manually using the -m flag, like in the example above.

I agree that the error message is not the best, the Array<Nullable<>> is not relevant and can cause confusion, but these types are indeed handled correctly, that is, removed when building the type string (source code)