A modern programming language that makes developers happier.

kotlinlang

hey all :wave: ! I was just wondering what the official stance of Exposed is with regards to vendor-specific features that aren't supported by all DBs and whether they should be included in the library itself or not. For example I saw that the tests contain a `class PGEnum` and while it is quite straightforward to implement an enum type mapping from that, it would be nice to have this out of the box. Similarly, there is a some code floating around for array columns and it can be adapted to also translate to columns of `Set&lt;T : Enum&gt;`  . I just took the liberty of bundling those up as <https://github.com/milgner/exposed-postgres> but it's also a bit obscure now and I think it could benefit more people if it was in the library itself. I haven't looked at the whole infrastructure for Exposed yet but I'd be willing to put in some additional work in order to integrate these extensions properly.