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

Don't require PostGIS unless using it as a search backend #195

Open
amercader opened this issue Feb 15, 2018 · 1 comment
Open

Don't require PostGIS unless using it as a search backend #195

amercader opened this issue Feb 15, 2018 · 1 comment

Comments

@amercader
Copy link
Member

There is absolutely no reason to require PostGIS if you are using one of the Solr backends. It's just required for historical reasons as it was the only backend supported initially.

The PostGIS search backend is not recommended anyway and the PostGIS install adds complexity and causes issues like ckan/ckan#3929 or #182.

@amercader
Copy link
Member Author

A bit of refactoring on plugin.py to not initialize the tables or store the extent if not using the postgis backend should be enough. And ideally add some tests using the solr backend.

amercader added a commit that referenced this issue Aug 24, 2022
Consolidate all DB related modules and functions into a single module
for easier encapsulation. The PostGIS database table and the functions
to store PostGIS geometries are no longer called by default.

There is a new config option (`ckan.spatial.use_postgis=true`) to
re-enable this behaviour. This option (and the actual PostGIS modules)
will be dropped in future versions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant