My apologies if this is in the wrong place, or if I don't have enough information. This just seemed the most likely package where the issue was occurring.

I have two databases that I am connection to, that both have custom enumeration types. If I new up the first database connection, and access it, then new up a database connection for the second one, and access it, the second one then throws an error, trying to convert the enumeration to an Int32, which is incorrect behavior.

Conversely, if instead both database connections are made first, then are accessed, it does not attempt to convert to an Int32, and everything runs smoothly.

I know this doesn't make a lot of sense, so I created a test project that showcases what is happening, and can be found here: https://github.com/alex-polosky/cs-dotnet-ef-npgsql-multi-db-error

Please let me know if I made this issue in the wrong area, or if anyone thinks it could be an issue with the core Npgsql solution instead. Also, let me know if I need to shave off more code, I know that I have a data access layer in between the access and database connection, however I presume that it'd throw the same error. Actually, that might make for a good test.3 project.