When an invalid column name is used to define an enum constant, the present behaviour is to print a warning and continue. This can get lost in the startup noise. I assume this behaviour was to permit loading for migrations. Since we now have harder initialisation failure, and the ability to ignore this to run migrations, we should consider using this for invalid columns too.

== works, but using as a hash key does not.