Fixing connection prefix bug #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

ChrisThompsonTLDR wants to merge 1 commit into grimzy:master

from ChrisThompsonTLDR:patch-1

Open

Fixing connection prefix bug #162

ChrisThompsonTLDR wants to merge 1 commit into grimzy:master from ChrisThompsonTLDR:patch-1

Conversation

ChrisThompsonTLDR

Copy link

@ChrisThompsonTLDR ChrisThompsonTLDR commented Dec 3, 2020

The package's overloading of the Blueprint object pummels defined prefixes for the configured connection. This causes migrations to not respect table and index prefix.

Reference https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Schema/Builder.php#L347

@ChrisThompsonTLDR


 Fixing connection prefix bug

411dc3e

The package's overloading of the `Blueprint` object pummels defined prefixes for the configured connection. This causes migrations to not respect table and index prefix.
Reference https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Schema/Builder.php#L347

@ChrisThompsonTLDR

Copy link

Author