adwhit

The line ``` + account_status -> AccountStatus, ``` should read ``` + account_status -> AccountStatusMapping, ``` Take a look at the README for more information.

This is a basic problem with how Diesel generates a schema and is not really under control of this crate. There is a suggested solution here: https://github.com/adwhit/diesel-derive-enum/issues/53. Basically, make a...

Ah, I see you are using MariaDB. It seems that Diesel does it's enum name mangling differently to Postgres. Your options are to a) re-export `AccountStatusMapping` as `Enum` inside your...

The fundamental problem is that when generating the schema, Diesel looks at the database and decides that your type should be given the name `Enum`. This crate unfortunately cannot control...

I should add that this crate is intended to support every database that Diesel supports. But it happens to be that Postgres has the best support for enums and thus...

This is nice but I think as content it is more appropriate for the main `diesel` docs. This crate has no particular opinion on how to structure your application.

I've thought about this a bit more and actually it's the cleanest solution to the problem of auto-generated diesel types not matching up with mapping names. So I think I...

Hmm. What do you think should happen with an empty enum, hard failure? I agree that a warning isn't very helpful.

Yes, I suppose the easiest thing to do it just remove the match block if there are no variants. No idea if that is really useful to anyone but it...

Hi, yeah there is some kind of problem with isolating the tables in Postgres. I think the problem is that `CREATE TYPE ENUM` is not local to the (temporary) schema....