Use the schema defined in the Laravel configuration

[grimzy]

PR for #96.

Possibly breaks the fix for #68 (#70) because if forces the Laravel/Laravel-postgis to use the schema set in the database configuration ('database.connections.pgsql.schema')

[coveralls]

Coverage decreased (-2.3%) to 81.651% when pulling e2c786d on grimzy:master into b751206 on njbarrett:master.

[grimzy]

Oops! Fixing this in a little bit.

[grimzy]

FYI, the tests are not passing although the solution works as expected.
I'm not sure how to unit test a Laravel package when using the config helper and/or facade (probably have to initialize a Laravel App instance during the tests with use CreatesApplication;).

[grimzy]

Pushed another commit, this time using a configuration file to set the schema to use for Postgis.

In general, I don't think that the Postgis functions should be prefixed with the schema when performing queries through Eloquent. Instead someone with the issue mentioned in #68 should try to add the alternate schema (where Postgis is loaded) to the search_path:

$schema_name = 'default_schema';
$postgis_schema = 'postgis_schema';
DB::statement("SET search_path = $schema_name, $postgis_schema");

What do you think?

[njbarrett]

Thanks for this, I agree that hardcoding public was not a great solution, and think your config method is better.

I'll merge this and then see if I can assist fixing the tests.