> What do you mean by that? Sure this is some kind of failure as the column type extracted from the column comment isn't known to Doctrine (anymore). The question is what do in this case. You could throw an exception here (which is the current behaviour) or fall back to the native database type (which is what this PR does).

I'd prefer an exception to be thrown - if a type doesn't exist, then either the application code or the DB have to be updated

Can't really do it silently like that. What can be done here is throwing a specialized exception with a clear exception message instead.