I have found the issue. In Illuminate\Database\Schema\MySqlBuilder::hasTable(), the $table variable already comes with the prefix, but another prefix is being appended within the function. This might be the result of a fix done for this issue: #3, as I'm noticing the first prefix was appended in Illuminate\Database\Migrations\DatabaseMigrationRepository::repositoryExists()

That has been changed two days ago because of a recent issue someone posted (see #2031)

Yup, solved the problem for me to remove the extra prefix in the Illuminate\Database\Migrations\DatabaseMigrationRepository line 140#

I'm running into this one too. Amending method DatabaseMigrationRepository::repositoryExists() to not pass along the prefix works...

Fixed.

I think in latest Laravel version this bug comes again. At least it reproduces for me with Postgres databases.

No need to set the prefix there I don't think. If you have a prefix
configured in your database configuration settings it should carry over to
migrations.

On Wed, Jan 21, 2015 at 3:10 AM, Vladislav Rastrusny <
[email protected]> wrote:

I think in latest Laravel version this bug comes again. At least it
reproduces for me with Postgres databases.

—
Reply to this email directly or view it on GitHub
#2043 (comment).

I think not everyone stores migration table in the same schema as all other project data.

@FractalizeR +1