I've tried to run a quick check for 5.0 - but it seems that DB dialect autodetection have changed since 4.x so I think this issue can probably be closed.