You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: