Skip to content
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

Enable/Disable Postgis without a table #77

Merged
merged 1 commit into from
Jun 20, 2017

Conversation

grimzy
Copy link
Contributor

@grimzy grimzy commented Jun 20, 2017

Currently, to use migrations to enable or disable Postgis requires a table:

Schema::create('some_table', function (Blueprint $table) {
    $table->enablePostgis();
});

This pull request enables the use of Schema::enablePostgis() and Schema::disablePostgis() directly on the schema which makes more sense.

@coveralls
Copy link

coveralls commented Jun 20, 2017

Coverage Status

Changes Unknown when pulling 88c3d10 on grimzy:extension-on-schema into ** on njbarrett:master**.

@njbarrett
Copy link
Collaborator

This looks good, thanks for your contribution!

@njbarrett njbarrett merged commit 257f4df into mstaack:master Jun 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants