Vague error message when Doctrine is involved

[shaedrich]

Is there a good reason, why it says

{$name}: failed to dump queries. This may be due to changing database columns using Doctrine, which is not supported while pretending to run migrations.

when running php artisan migrate --pretend and Doctrine is involved instead of outputting $e->getMessage(). It doesn't feel right to overgeneralize. This error message could mean anything while $e->getMessage() contains pretty helpful information

framework/src/Illuminate/Database/Migrations/Migrator.php

Lines 413 to 432 in edb438a

	protected function pretendToRun($migration, $method)
	{
	try {
	foreach ($this->getQueries($migration, $method) as $query) {
	$name = get_class($migration);
	$reflectionClass = new ReflectionClass($migration);
	if ($reflectionClass->isAnonymous()) {
	$name = $this->getMigrationName($reflectionClass->getFileName());
	}
	$this->note("<info>{$name}:</info> {$query['query']}");
	}
	} catch (SchemaException $e) {
	$name = get_class($migration);
	$this->note("<info>{$name}:</info> failed to dump queries. This may be due to changing database columns using Doctrine, which is not supported while pretending to run migrations.");
	}
	}

[shaedrich]

Since Laravel is moving away from Doctrine, this, too, might be a thing of the past in the future.